[GUMP@vmgump]: Project tomcat-tc7.0.x-test (in module tomcat-7.0.x) failed
To whom it may engage... This is an automated request, but not an unsolicited one. For more information please visit http://gump.apache.org/nagged.html, and/or contact the folk at gene...@gump.apache.org. Project tomcat-tc7.0.x-test has an issue affecting its community integration. This issue affects 1 projects, and has been outstanding for 2 runs. The current state of this project is 'Failed', with reason 'Build Failed'. For reference only, the following projects are affected by this: - tomcat-tc7.0.x-test : Tomcat 7.x, a web server implementing Java Servlet 3.0, ... Full details are available at: http://vmgump.apache.org/gump/public/tomcat-7.0.x/tomcat-tc7.0.x-test/index.html That said, some information snippets are provided here. The following annotations (debug/informational/warning/error messages) were provided: -DEBUG- Dependency on tomcat-tc7.0.x-dbcp exists, no need to add for property tomcat-dbcp-src.jar. -DEBUG- Dependency on commons-daemon exists, no need to add for property commons-daemon.native.src.tgz. -DEBUG- Dependency on commons-daemon exists, no need to add for property tomcat-native.tar.gz. -DEBUG- Dependency on tomcat-tc7.0.x-dbcp exists, no need to add for property tomcat-dbcp.home. -INFO- Failed with reason build failed -INFO- Project Reports in: /srv/gump/public/workspace/tomcat-7.0.x/output/build/logs The following work was performed: http://vmgump.apache.org/gump/public/tomcat-7.0.x/tomcat-tc7.0.x-test/gump_work/build_tomcat-7.0.x_tomcat-tc7.0.x-test.html Work Name: build_tomcat-7.0.x_tomcat-tc7.0.x-test (Type: Build) Work ended in a state of : Failed Elapsed: 21 mins 50 secs Command Line: /usr/lib/jvm/java-6-openjdk/bin/java -Djava.awt.headless=true -Dbuild.sysclasspath=only org.apache.tools.ant.Main -Dgump.merge=/srv/gump/public/gump/work/merge.xml -Djunit.jar=/srv/gump/public/workspace/junit/dist/junit-03042012.jar -Dcommons-daemon.native.src.tgz=/srv/gump/public/workspace/apache-commons/daemon/dist/bin/commons-daemon-03042012-native-src.tar.gz -Dtomcat-native.tar.gz=/srv/gump/public/workspace/apache-commons/daemon/dist/bin/commons-daemon-03042012-native-src.tar.gz -Dexamples.sources.skip=true -Dtomcat-dbcp.home=/srv/gump/public/workspace/tomcat-7.0.x/tomcat-deps -Djdt.jar=/srv/gump/packages/eclipse/plugins/org.eclipse.jdt.core_3.4.2/jdtcore.jar -Dcommons-daemon.jar=/srv/gump/public/workspace/apache-commons/daemon/dist/commons-daemon-03042012.jar -Dtomcat-dbcp-src.jar=/srv/gump/public/workspace/tomcat-7.0.x/tomcat-deps/tomcat-dbcp-src.jar -Dtest.accesslog=true -Dcommons-pool.home=/srv/gump/public/workspace/commons-pool-1.x -Dcommons-dbcp.home=/ srv/gump/public/workspace/commons-dbcp-1.x -Dtomcat-dbcp.jar=/srv/gump/public/workspace/tomcat-7.0.x/tomcat-deps/tomcat-dbcp-03042012.jar test [Working Directory: /srv/gump/public/workspace/tomcat-7.0.x] CLASSPATH: /usr/lib/jvm/java-6-openjdk/lib/tools.jar:/srv/gump/public/workspace/tomcat-7.0.x/output/build/webapps/examples/WEB-INF/classes:/srv/gump/public/workspace/tomcat-7.0.x/output/testclasses:/srv/gump/public/workspace/ant/dist/lib/ant.jar:/srv/gump/public/workspace/ant/dist/lib/ant-launcher.jar:/srv/gump/public/workspace/ant/dist/lib/ant-jmf.jar:/srv/gump/public/workspace/ant/dist/lib/ant-junit.jar:/srv/gump/public/workspace/ant/dist/lib/ant-swing.jar:/srv/gump/public/workspace/ant/dist/lib/ant-apache-resolver.jar:/srv/gump/public/workspace/ant/dist/lib/ant-apache-xalan2.jar:/srv/gump/public/workspace/xml-commons/java/build/resolver.jar:/srv/gump/public/workspace/tomcat-7.0.x/output/build/bin/bootstrap.jar:/srv/gump/public/workspace/tomcat-7.0.x/output/build/bin/tomcat-juli.jar:/srv/gump/public/workspace/tomcat-7.0.x/output/build/lib/annotations-api.jar:/srv/gump/public/workspace/tomcat-7.0.x/output/build/lib/servlet-api.jar:/srv/gump/public/workspace/tomcat-7.0.x/outp ut/build/lib/jsp-api.jar:/srv/gump/public/workspace/tomcat-7.0.x/output/build/lib/el-api.jar:/srv/gump/public/workspace/tomcat-7.0.x/output/build/lib/catalina.jar:/srv/gump/public/workspace/tomcat-7.0.x/output/build/lib/catalina-ant.jar:/srv/gump/public/workspace/tomcat-7.0.x/output/build/lib/tomcat-coyote.jar:/srv/gump/public/workspace/tomcat-7.0.x/output/build/lib/jasper.jar:/srv/gump/public/workspace/tomcat-7.0.x/output/build/lib/jasper-el.jar:/srv/gump/public/workspace/tomcat-7.0.x/output/build/lib/catalina-tribes.jar:/srv/gump/public/workspace/tomcat-7.0.x/output/build/lib/catalina-ha.jar:/srv/gump/public/workspace/tomcat-7.0.x/output/build/lib/tomcat-api.jar:/srv/gump/public/workspace/tomcat-7.0.x/output/build/lib/tomcat-util.jar:/srv/gump/packages/javamail-1.4/mail.jar:/srv/gump/packages/javamail-1.4/lib/mailapi.jar:/srv/gump/packages/jaf-1.1ea/activation.jar:/srv/gump/packages/eclipse/plugins/org.eclipse.jdt.core_3.4.2/jdtcore.jar:/srv/gump/public/workspace/tomcat-7.
[GUMP@vmgump]: Project tomcat-trunk-test (in module tomcat-trunk) failed
To whom it may engage... This is an automated request, but not an unsolicited one. For more information please visit http://gump.apache.org/nagged.html, and/or contact the folk at gene...@gump.apache.org. Project tomcat-trunk-test has an issue affecting its community integration. This issue affects 1 projects, and has been outstanding for 2 runs. The current state of this project is 'Failed', with reason 'Build Failed'. For reference only, the following projects are affected by this: - tomcat-trunk-test : Tomcat 8.x, a web server implementing Java Servlet 3.1, ... Full details are available at: http://vmgump.apache.org/gump/public/tomcat-trunk/tomcat-trunk-test/index.html That said, some information snippets are provided here. The following annotations (debug/informational/warning/error messages) were provided: -DEBUG- Dependency on tomcat-trunk-dbcp exists, no need to add for property tomcat-dbcp-src.jar. -DEBUG- Dependency on commons-daemon exists, no need to add for property commons-daemon.native.src.tgz. -DEBUG- Dependency on commons-daemon exists, no need to add for property tomcat-native.tar.gz. -DEBUG- Dependency on tomcat-trunk-dbcp exists, no need to add for property tomcat-dbcp.home. -INFO- Failed with reason build failed -INFO- Project Reports in: /srv/gump/public/workspace/tomcat-trunk/output/build/logs The following work was performed: http://vmgump.apache.org/gump/public/tomcat-trunk/tomcat-trunk-test/gump_work/build_tomcat-trunk_tomcat-trunk-test.html Work Name: build_tomcat-trunk_tomcat-trunk-test (Type: Build) Work ended in a state of : Failed Elapsed: 22 mins 17 secs Command Line: /usr/lib/jvm/java-6-openjdk/bin/java -Djava.awt.headless=true -Dbuild.sysclasspath=only org.apache.tools.ant.Main -Dgump.merge=/srv/gump/public/gump/work/merge.xml -Djunit.jar=/srv/gump/public/workspace/junit/dist/junit-03042012.jar -Dcommons-daemon.native.src.tgz=/srv/gump/public/workspace/apache-commons/daemon/dist/bin/commons-daemon-03042012-native-src.tar.gz -Dtomcat-native.tar.gz=/srv/gump/public/workspace/apache-commons/daemon/dist/bin/commons-daemon-03042012-native-src.tar.gz -Dexamples.sources.skip=true -Dtomcat-dbcp.home=/srv/gump/public/workspace/tomcat-trunk/tomcat-deps -Djdt.jar=/srv/gump/packages/eclipse/plugins/org.eclipse.jdt.core_3.4.2/jdtcore.jar -Dcommons-daemon.jar=/srv/gump/public/workspace/apache-commons/daemon/dist/commons-daemon-03042012.jar -Dtomcat-dbcp-src.jar=/srv/gump/public/workspace/tomcat-trunk/tomcat-deps/tomcat-dbcp-src.jar -Dtest.accesslog=true -Dcommons-pool.home=/srv/gump/public/workspace/commons-pool-1.x -Dcommons-dbcp.home=/ srv/gump/public/workspace/commons-dbcp-1.x -Dtomcat-dbcp.jar=/srv/gump/public/workspace/tomcat-trunk/tomcat-deps/tomcat-dbcp-03042012.jar test [Working Directory: /srv/gump/public/workspace/tomcat-trunk] CLASSPATH: /usr/lib/jvm/java-6-openjdk/lib/tools.jar:/srv/gump/public/workspace/tomcat-trunk/output/build/webapps/examples/WEB-INF/classes:/srv/gump/public/workspace/tomcat-trunk/output/testclasses:/srv/gump/public/workspace/ant/dist/lib/ant.jar:/srv/gump/public/workspace/ant/dist/lib/ant-launcher.jar:/srv/gump/public/workspace/ant/dist/lib/ant-jmf.jar:/srv/gump/public/workspace/ant/dist/lib/ant-junit.jar:/srv/gump/public/workspace/ant/dist/lib/ant-swing.jar:/srv/gump/public/workspace/ant/dist/lib/ant-apache-resolver.jar:/srv/gump/public/workspace/ant/dist/lib/ant-apache-xalan2.jar:/srv/gump/public/workspace/xml-commons/java/build/resolver.jar:/srv/gump/public/workspace/tomcat-trunk/output/build/bin/bootstrap.jar:/srv/gump/public/workspace/tomcat-trunk/output/build/bin/tomcat-juli.jar:/srv/gump/public/workspace/tomcat-trunk/output/build/lib/annotations-api.jar:/srv/gump/public/workspace/tomcat-trunk/output/build/lib/servlet-api.jar:/srv/gump/public/workspace/tomcat-trunk/outp ut/build/lib/jsp-api.jar:/srv/gump/public/workspace/tomcat-trunk/output/build/lib/el-api.jar:/srv/gump/public/workspace/tomcat-trunk/output/build/lib/catalina.jar:/srv/gump/public/workspace/tomcat-trunk/output/build/lib/catalina-ant.jar:/srv/gump/public/workspace/tomcat-trunk/output/build/lib/tomcat-coyote.jar:/srv/gump/public/workspace/tomcat-trunk/output/build/lib/jasper.jar:/srv/gump/public/workspace/tomcat-trunk/output/build/lib/jasper-el.jar:/srv/gump/public/workspace/tomcat-trunk/output/build/lib/catalina-tribes.jar:/srv/gump/public/workspace/tomcat-trunk/output/build/lib/catalina-ha.jar:/srv/gump/public/workspace/tomcat-trunk/output/build/lib/tomcat-api.jar:/srv/gump/public/workspace/tomcat-trunk/output/build/lib/tomcat-jni.jar:/srv/gump/public/workspace/tomcat-trunk/output/build/lib/tomcat-util.jar:/srv/gump/packages/javamail-1.4/mail.jar:/srv/gump/packages/javamail-1.4/lib/mailapi.jar:/srv/gump/packages/jaf-1.1ea/activation.jar:/srv/gump/packages/eclipse/plugins/org
Re: [VOTE] Release Apache Tomcat 7.0.27
On 02.04.2012 22:29, Mark Thomas wrote: On 02/04/2012 19:30, Mark Thomas wrote: On 01/04/2012 15:26, Rainer Jung wrote: - AJP via httpd + mod_jk to BIO, NIO and APR/native - AJP via httpd + mod_proxy_ajp to BIO, NIO and APR/native I'm curious: which mod_jk version did you use? 1.2.31 I am mainly concerned about the AJP implementation on the Java side but I should probably update that to 1.2.35. I just re-ran the 7.0.27 RC through the Servlet 3.0 TCK with httpd + mod_jk 1.2.35 and all three AJP connectors (BIO, NIO, APR) and all tests passed. Good to know, thanks! Rainer - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
Who wants my Cassandra session manager for Tomcat?
All, I recently implemented a Tomcat session manager that uses Cassandra for session storage. Cassandra is a commonly used session store for PHP-based applications, but I could not find one that would plug seamlessly into Tomcat. My Cassandra session manager is fully working and has gone through basic testing. Now I want to donate my code to the Tomcat project - if you'll have it. I am unsure on how to proceed with this, so any direction will be very much appreciated. I did manage the donation of XSLTC from Sun Microsystems to the Xalan-J project at xml.apache.org way back when, but this was more than 10 years ago and my memory isn't great... Apologies if this is the wrong forum for this request. Best regards, Morten Jorgensen -- Morten Jørgensen Chief Architect *OpenJaw Technologies* T: + 353 (0)1 - 882 5444 W: www.openjawtech.com http://www.openjawtech.com/ Join OpenJaw Technologies Group on LinkedIn http://www.linkedin.com/groups?about=gid=4074413 / Follow OpenJawTech on Twitter http://twitter.com/#%21/OpenJawTech. We have checked this material for computer viruses and although none has been found by us, we cannot guarantee that it is completely virus free and we do not accept any liability for loss or damage that may be caused. Please therefore check any attachments for viruses before using them on your own equipment. If you do find a computer virus please inform us immediately so that we may take appropriate action. This communication is intended solely for the addressee and is confidential. If you are not the intended recipient, please delete this email. Any disclosure, copying, distribution or any action taken or omitted to be taken in reliance on it, is prohibited and may be unlawful. - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
Re: [VOTE] Release Apache Tomcat 7.0.27
2012/3/31 Mark Thomas ma...@apache.org: The proposed Apache Tomcat 7.0.27 release is now available for voting. It can be obtained from: https://dist.apache.org/repos/dist/dev/tomcat/tomcat-7/v7.0.27/ The Maven staging repo is: https://repository.apache.org/content/repositories/orgapachetomcat-132/ The svn tag is: http://svn.apache.org/repos/asf/tomcat/tc7.0.x/tags/TOMCAT_7_0_27/ Quick testing, install uninstall - OK on Windows (WinXP and Win7) with 32-bit JRE 6u31. Testsuite run with BIO, NIO, APR connectors On WinXP with Oracle JDK 6u31 32-bit, Tomcat-Native 1.1.23 - all tests passed, except only one: The failed test: org.apache.catalina.loader.TestWebappClassLoaderExecutorMemoryLeak It failed with BIO. On a rerun it failed with BIO and NIO. So it is reproducible and it is occasional and I think it does not matter what connector is used. Testcase: testTimerThreadLeak took 2,547 sec FAILED null junit.framework.AssertionFailedError: null at org.apache.catalina.loader.TestWebappClassLoaderExecutorMemoryLeak.testTimerThreadLeak(TestWebappClassLoaderExecutorMemoryLeak.java:72) The code there tests Executor state. Maybe the test itself is wrong and there should be some pause before Executor terminates: L71:Assert.assertTrue(executorServlet.tpe.isShutdown()); L72:Assert.assertTrue(executorServlet.tpe.isTerminated()); Anyway I do not see how this could noticeably impact Tomcat functionality. [x] Stable - go ahead and release as 7.0.27 Stable Best regards, Konstantin Kolinko - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
Re: Who wants my Cassandra session manager for Tomcat?
On 03/04/2012 09:56, Morten Jorgensen wrote: All, I recently implemented a Tomcat session manager that uses Cassandra for session storage. Cassandra is a commonly used session store for PHP-based applications, but I could not find one that would plug seamlessly into Tomcat. My Cassandra session manager is fully working and has gone through basic testing. That's interesting. Can you share some details about how it works? p Now I want to donate my code to the Tomcat project - if you'll have it. I am unsure on how to proceed with this, so any direction will be very much appreciated. I did manage the donation of XSLTC from Sun Microsystems to the Xalan-J project at xml.apache.org way back when, but this was more than 10 years ago and my memory isn't great... Apologies if this is the wrong forum for this request. Best regards, Morten Jorgensen -- [key:62590808] signature.asc Description: OpenPGP digital signature
Re: Who wants my Cassandra session manager for Tomcat?
On 03/04/2012 09:56, Morten Jorgensen wrote: All, I recently implemented a Tomcat session manager that uses Cassandra for session storage. Cassandra is a commonly used session store for PHP-based applications, but I could not find one that would plug seamlessly into Tomcat. My Cassandra session manager is fully working and has gone through basic testing. Now I want to donate my code to the Tomcat project - if you'll have it. I am unsure on how to proceed with this, so any direction will be very much appreciated. I did manage the donation of XSLTC from Sun Microsystems to the Xalan-J project at xml.apache.org way back when, but this was more than 10 years ago and my memory isn't great... I can't speak for the committers/project, but one option would be to file an enhancement request and attach a patch in diff format. Whether it gets added or not would depend on the committers' opinion about the value of the feature the impact of adding dependencies etc. Is there a community of users already, or is it too new? Apologies if this is the wrong forum for this request. It's the right forum. p Best regards, Morten Jorgensen -- [key:62590808] signature.asc Description: OpenPGP digital signature
Re: Who wants my Cassandra session manager for Tomcat?
Hi, Maybe it should be posted to cassandra list? - Romain Le 3 avr. 2012 18:52, Pid p...@pidster.com a écrit : On 03/04/2012 09:56, Morten Jorgensen wrote: All, I recently implemented a Tomcat session manager that uses Cassandra for session storage. Cassandra is a commonly used session store for PHP-based applications, but I could not find one that would plug seamlessly into Tomcat. My Cassandra session manager is fully working and has gone through basic testing. Now I want to donate my code to the Tomcat project - if you'll have it. I am unsure on how to proceed with this, so any direction will be very much appreciated. I did manage the donation of XSLTC from Sun Microsystems to the Xalan-J project at xml.apache.org way back when, but this was more than 10 years ago and my memory isn't great... I can't speak for the committers/project, but one option would be to file an enhancement request and attach a patch in diff format. Whether it gets added or not would depend on the committers' opinion about the value of the feature the impact of adding dependencies etc. Is there a community of users already, or is it too new? Apologies if this is the wrong forum for this request. It's the right forum. p Best regards, Morten Jorgensen -- [key:62590808]
Re: Who wants my Cassandra session manager for Tomcat?
I would tend to view a Cassandra session manager as secondary to the notion of a simple and extensible session manager interface that is fundamentally disconnected from the tomcat infrastructure. It would be valuable to use class serialization and session information in a cross platform way across ruby, php, and even C++. On 03/04/2012 09:56, Morten Jorgensen wrote: All, I recently implemented a Tomcat session manager that uses Cassandra for session storage. Cassandra is a commonly used session store for PHP-based applications, but I could not find one that would plug seamlessly into Tomcat. My Cassandra session manager is fully working and has gone through basic testing. Now I want to donate my code to the Tomcat project - if you'll have it. I am unsure on how to proceed with this, so any direction will be very much appreciated. I did manage the donation of XSLTC from Sun Microsystems to the Xalan-J project at xml.apache.org way back when, but this was more than 10 years ago and my memory isn't great... I can't speak for the committers/project, but one option would be to file an enhancement request and attach a patch in diff format. Whether it gets added or not would depend on the committers' opinion about the value of the feature the impact of adding dependencies etc. Is there a community of users already, or is it too new? Apologies if this is the wrong forum for this request. It's the right forum. p Best regards, Morten Jorgensen -- [key:62590808] - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
Re: Who wants my Cassandra session manager for Tomcat?
Pid, On 4/3/12 12:52 PM, Pid wrote: I can't speak for the committers/project, but one option would be to file an enhancement request and attach a patch in diff format. +1 To get such a thing into Tomcat, it would probably have to have the following features: 1. Be relatively self-contained -- i.e. not require much in the way of changes to existing classes 2. Not have any external dependencies (new JAR files, etc.). This might be a problem, depending on whether your code uses the REST API for Cassandra or a direct Java binding. 3. Include good documentation for how to set it up. See the existing session-persistence documentation for a guide, and aim to do a better job ;) 4. Include test cases and potentially instructions for setting-up a test environment (i.e. you're gonna need a working Cassandra instance). If the above are not met, you'll likely get a lot of push-back, including mine. I know there's a lurker on this list who maintains a memcached-oriented session manager and we've never really considered including that in Tomcat because of (I'd imagine) dependency issues. In any case, even if it doesn't get included in Tomcat, you could always post it to the Wiki as contributed code. Just make sure you include great documentation otherwise nobody will ever use it. Thanks, -chris signature.asc Description: OpenPGP digital signature
DO NOT REPLY [Bug 53024] Accessing Servlet while Reloading context gives 404 error
https://issues.apache.org/bugzilla/show_bug.cgi?id=53024 Christopher Schultz ch...@christopherschultz.net changed: What|Removed |Added OS/Version||All --- Comment #1 from Christopher Schultz ch...@christopherschultz.net 2012-04-03 20:24:28 UTC --- Do you have any evidence to support a regression claim? Test case? -- Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
DO NOT REPLY [Bug 52791] [PATCH] read windows installer default values from config file
https://issues.apache.org/bugzilla/show_bug.cgi?id=52791 Konstantin Kolinko knst.koli...@gmail.com changed: What|Removed |Added OS/Version||All --- Comment #2 from Konstantin Kolinko knst.koli...@gmail.com 2012-04-03 20:40:29 UTC --- -1 for hard-coded filename of config.ini. IMHO the name of the answer file should be passed on the command line. If no name is given then there should be no attempts to open and read the file. (Is is possible to read the file just once, instead of re-opening and re-scanning it for each config option? It is not as bad if this behaviour is off by default. it is just that it does not scale well. Maybe read the file into memory and do string scans there?) The names: _Call, _String, _Result, _Default -- are you sure that they are unique? They look like polluting the name space. -- Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
Re: Who wants my Cassandra session manager for Tomcat?
On 03/04/2012 21:08, Christopher Schultz wrote: Pid, On 4/3/12 12:52 PM, Pid wrote: I can't speak for the committers/project, but one option would be to file an enhancement request and attach a patch in diff format. +1 To get such a thing into Tomcat, it would probably have to have the following features: 1. Be relatively self-contained -- i.e. not require much in the way of changes to existing classes 2. Not have any external dependencies (new JAR files, etc.). This might be a problem, depending on whether your code uses the REST API for Cassandra or a direct Java binding. 3. Include good documentation for how to set it up. See the existing session-persistence documentation for a guide, and aim to do a better job ;) 4. Include test cases and potentially instructions for setting-up a test environment (i.e. you're gonna need a working Cassandra instance). If the above are not met, you'll likely get a lot of push-back, including mine. I know there's a lurker on this list who maintains a memcached-oriented session manager and we've never really considered including that in Tomcat because of (I'd imagine) dependency issues. In any case, even if it doesn't get included in Tomcat, you could always post it to the Wiki as contributed code. Just make sure you include great documentation otherwise nobody will ever use it. There is also ASF Extras or whatever the tertiary associated thing is called. p Thanks, -chris -- [key:62590808] signature.asc Description: OpenPGP digital signature
Re: Who wants my Cassandra session manager for Tomcat?
Thanks to all for your feedback. I am providing some additional information as requested: That's interesting. Can you share some details about how it works? Sure. It is quite simple. Cassandra is effectively a multi-level distributed hash-map, so it lends itself very well do storing session attributes. The session manager maintains two column families (like tables), one to hold session meta-data such as the last access timestamp, etc. and one column family to hold session attributes. Storing or reading a session attribute is simply a matter of writing it using the session ID as the row ID, and the session attribute name as the column name, and the session attribute value as the column value. Session attributes are read and written independently, so the entire web session does not have to be loaded into memory - only the session attributes that are actually required to service a request are read. This greatly reduces the memory footprint of the web applications that I am developing for my employer. For improved performance I have added a write-through and a write-back cache, implemented as servlet filters. The cache is flushed or written back once the current request has finished processing. I am sure there is room for improvement here, as multiple concurrent requests for the same session should be served using the same cache instance. The Manager does not maintain any references to Session instances at all, allowing them to be garbage collected at any time. This makes things very simple, as Cassandra holds all session state, and the session managers in my Tomcat nodes only act as a cache in front of Cassandra. The nature of Cassandra and the Tomcat's implementation of web sessions go together extremely well. I am surprised that nothing like this exists already. It is a square hole, square peg sort of scenario. I also have an implementation of the Map interface that stores the values of each entry as a session attribute. The way many developers write web applications is to have a session bean (a session attribute) that contains a Map that maintains the actual session attributes. This is OK if the entire session is persisted as a whole, but it won't perform very well with the Cassandra session manager (or the Delta Session Manager from what I understand). A developer can replace their session bean's HashMap with the SessionMap utility, and the session attributes will be treated as proper session attributes by the session manager. 1. Be relatively self-contained -- i.e. not require much in the way of changes to existing classes There are no changes to existing classes. My session manager implements the existing org.apache.catalina.Manager interface. 2. Not have any external dependencies (new JAR files, etc.). This might be a problem, depending on whether your code uses the REST API for Cassandra or a direct Java binding. This could be a problem... I use the Hector API to access Cassandra, and there are about 10 JARs required for this API. 3. Include good documentation for how to set it up. See the existing session-persistence documentation for a guide, and aim to do a better job ;) It is extremely easy to set up: 1) Configure your Cassandra ring (cluster). 2) Copy the required Hector API JARs and the Cassandra session manager JAR to tomcat/lib 3) Configure your web application descriptor to use the Cassandra session manager. Parameters in the web application descriptor point the session manager to one or more nodes in your Cassandra ring. 4. Include test cases and potentially instructions for setting-up a test environment (i.e. you're gonna need a working Cassandra instance). This is pretty much non-existent right now, so I'll put some effort in there. What format do you guys use for your documentation? Do you still use docbook? Thanks again for all your comments and feedback. Morten - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
DO NOT REPLY [Bug 53031] New: Jasper Ant task should support Fork option
https://issues.apache.org/bugzilla/show_bug.cgi?id=53031 Bug #: 53031 Summary: Jasper Ant task should support Fork option Product: Tomcat 6 Version: 6.0.35 Platform: All OS/Version: All Status: NEW Severity: enhancement Priority: P2 Component: Jasper AssignedTo: dev@tomcat.apache.org ReportedBy: nicho...@nicholaswilliams.net Classification: Unclassified As discussed in the Ant Tasks Question thread posted to the users list (http://mail-archives.apache.org/mod_mbox/tomcat-users/201203.mbox/%3C00c82ddd5a8b1fb9cb75b0c98b39598d%40mail.gmail.com%3E), JspC has a getFork() method that unconditionally returns false. The JspC Ant task does not support forking like other Ant tasks, such as java, javac, etc. It is the opinion of at least myself and Chris Schultz that supporting forking should be expected of a nice player in the Ant ecosystem. The Ant task for JSP compilation should be improved to support forking. -- Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
DO NOT REPLY [Bug 53031] Ant Jasper task should support Fork option
https://issues.apache.org/bugzilla/show_bug.cgi?id=53031 Nick Williams nicho...@nicholaswilliams.net changed: What|Removed |Added Summary|Jasper Ant task should |Ant Jasper task should |support Fork option |support Fork option -- Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
DO NOT REPLY [Bug 53032] New: Ant Jasper task fails to run when using XML namespaces; no output; no errors
https://issues.apache.org/bugzilla/show_bug.cgi?id=53032
Bug #: 53032
Summary: Ant Jasper task fails to run when using XML
namespaces; no output; no errors
Product: Tomcat 6
Version: 6.0.35
Platform: All
OS/Version: All
Status: NEW
Severity: normal
Priority: P2
Component: Jasper
AssignedTo: dev@tomcat.apache.org
ReportedBy: nicho...@nicholaswilliams.net
Classification: Unclassified
One way to use bulk task definitions in Ant is to use XML namespaces:
project name=teamcity
xmlns:tomcat6=http://tomcat.apache.org/ant/tomcat/6;
...
path id=tomcat.6.ant.classpath
fileset dir=${my.path.library.build}/tomcat-6.0.35
include name=*.jar /
/fileset
path refid=my.path.compile.jsp /
/path
typedef resource=org/apache/catalina/ant/antlib.xml
uri=http://tomcat.apache.org/ant/tomcat/6;
classpathref=tomcat.6.ant.classpath /
...
target
tomcat6:list ... /
tomcat6:deploy ... /
/target
...
/project
This works great for list, deploy, etc. In fact, it works great for every other
Ant task as far as I can tell. But it doesn't work for the jasper/jasper2 tasks
(which both point to the same class).
tomcat6:jasper ... /
This does nothing. And by “nothing” I mean that I use `ant -verbose` when
running Ant, verbose=”1” within the Jasper task, and there’s no output from the
Jasper task, not a single line of output/logging, and the build completes in 0
seconds with no compiled JSPs output.
However, if I define the Jasper task explicitly, using the exact same paths (as
you can clearly see):
taskdef classname=org.apache.jasper.JspC name=tomcat6-jsp-compile
classpath
path refid=tomcat.6.ant.classpath /
/classpath
/taskdef
And call the Jasper task using the exact same options:
tomcat6-jsp-compile ... /
Everything works. It compiles 2,487 JSPs in 275s, and outputs exactly what I
expect, including 2,487 compiled JSPs and two logging messages. From what I
understand about Ant, there should be absolutely no difference, and yet there
apparently is, because they behave differently.
The jasper task should support namespaces like the other Tomcat Ant tasks, and
like other Ant tasks in general.
(Note: I have confirmed at http://ant.apache.org/faq.html that a separate
classloader IS used for the taskdef, and that Jspc will not have access to
conflicting classes loaded by other namespaces.)
--
Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email
--- You are receiving this mail because: ---
You are the assignee for the bug.
-
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org
DO NOT REPLY [Bug 53012] Ant Jasper task does not name including file when included file has compile error
https://issues.apache.org/bugzilla/show_bug.cgi?id=53012 --- Comment #1 from Nick Williams nicho...@nicholaswilliams.net 2012-04-03 22:02:12 UTC --- Relevant to 53011, 53012, 53031 and 53032: Per discussions with Chris Schultz in the users list, we agree that it would probably make more sense to separate the Ant task from the JspC class and place a new Ant task in the o.a.catalina.ant package (possibly o.a.catalina.ant.jasper?). Research about the state of the task needs to be completed. Further discussions about this will take place in the developer's list, and then these issues will be updated when a consensus is reached. -- Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
DO NOT REPLY [Bug 53011] Ant Jasper task fails after one error
https://issues.apache.org/bugzilla/show_bug.cgi?id=53011 --- Comment #2 from Nick Williams nicho...@nicholaswilliams.net 2012-04-03 22:06:04 UTC --- Note: While I don't disagree with your suggestion, Chris, and we can certainly discuss it further, that's not how Ant's javac works. Javac failonerror defaults to true, and when it's set to true, the behavior is to try compiling everything and wait until all compile errors have happened before failing. In fact, as far as I can tell, there is actually no way to make it behave like JspC (fail after the first error). Relevant to 53011, 53012, 53031 and 53032: Per discussions with Chris Schultz in the users list, we agree that it would probably make more sense to separate the Ant task from the JspC class and place a new Ant task in the o.a.catalina.ant package (possibly o.a.catalina.ant.jasper?). Research about the state of the task needs to be completed. Further discussions about this will take place in the developer's list, and then these issues will be updated when a consensus is reached. -- Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
DO NOT REPLY [Bug 53031] Ant Jasper task should support Fork option
https://issues.apache.org/bugzilla/show_bug.cgi?id=53031 --- Comment #1 from Nick Williams nicho...@nicholaswilliams.net 2012-04-03 22:07:01 UTC --- Relevant to 53011, 53012, 53031 and 53032: Per discussions with Chris Schultz in the users list, we agree that it would probably make more sense to separate the Ant task from the JspC class and place a new Ant task in the o.a.catalina.ant package (possibly o.a.catalina.ant.jasper?). Research about the state of the task needs to be completed. Further discussions about this will take place in the developer's list, and then these issues will be updated when a consensus is reached. -- Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
DO NOT REPLY [Bug 53032] Ant Jasper task fails to run when using XML namespaces; no output; no errors
https://issues.apache.org/bugzilla/show_bug.cgi?id=53032 --- Comment #1 from Nick Williams nicho...@nicholaswilliams.net 2012-04-03 22:07:09 UTC --- Relevant to 53011, 53012, 53031 and 53032: Per discussions with Chris Schultz in the users list, we agree that it would probably make more sense to separate the Ant task from the JspC class and place a new Ant task in the o.a.catalina.ant package (possibly o.a.catalina.ant.jasper?). Research about the state of the task needs to be completed. Further discussions about this will take place in the developer's list, and then these issues will be updated when a consensus is reached. -- Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
Re: Who wants my Cassandra session manager for Tomcat?
Morten, On 4/3/12 5:18 PM, Morten Jorgensen wrote: I also have an implementation of the Map interface that stores the values of each entry as a session attribute. The way many developers write web applications is to have a session bean (a session attribute) that contains a Map that maintains the actual session attributes. This is OK if the entire session is persisted as a whole, but it won't perform very well with the Cassandra session manager (or the Delta Session Manager from what I understand). A developer can replace their session bean's HashMap with the SessionMap utility, and the session attributes will be treated as proper session attributes by the session manager. This seems like something that is orthogonal to your Manager implementation, though quite useful. 1. Be relatively self-contained -- i.e. not require much in the way of changes to existing classes There are no changes to existing classes. My session manager implements the existing org.apache.catalina.Manager interface. Great. 2. Not have any external dependencies (new JAR files, etc.). This might be a problem, depending on whether your code uses the REST API for Cassandra or a direct Java binding. This could be a problem... I use the Hector API to access Cassandra, and there are about 10 JARs required for this API. Yeah, that could be a problem. I'm going to defer to the other devs for how tolerant we might be for such a thing to happen. It's possible that we could make this an optional module where it might be okay to have additional dependencies. 3. Include good documentation for how to set it up. See the existing session-persistence documentation for a guide, and aim to do a better job ;) It is extremely easy to set up: 1) Configure your Cassandra ring (cluster). 2) Copy the required Hector API JARs and the Cassandra session manager JAR to tomcat/lib 3) Configure your web application descriptor to use the Cassandra session manager. Parameters in the web application descriptor point the session manager to one or more nodes in your Cassandra ring. Presumably, you also need to set up Cassandra to have your column family (etc) definitions available. You'll obviously need to document what that is (or simply provide the configuration file, which should both document and specify at the same time). 4. Include test cases and potentially instructions for setting-up a test environment (i.e. you're gonna need a working Cassandra instance). This is pretty much non-existent right now, so I'll put some effort in there. What format do you guys use for your documentation? Do you still use docbook? Look at what's currently in the webapps/docs directory in svn. It's a fairly simple XML format that gets XSLT'd into .html files at release time. You could probably look at the existing docs for DeltaManager and BackupManager here http://tomcat.apache.org/tomcat-7.0-doc/config/cluster-manager.html and use them as a guide. Obviously, a Cassandra-based Session Manager can be used in a non-clustered environment to improve robustness and durability, so it might eventually go into its own separate config page instead of being on the cluster-manager.xml page. Go ahead and create a bugzilla entry for this and mention that a patch is forthcoming. When you submit a patch to Bugzilla, you have to grant rights to the ASF so that's better than just saying here's my Git repo or you can download my patch from my website. Obviously, don't include any of the binary dependencies: just mention what they are. -chris signature.asc Description: OpenPGP digital signature
DO NOT REPLY [Bug 53011] Ant Jasper task fails after one error
https://issues.apache.org/bugzilla/show_bug.cgi?id=53011 --- Comment #3 from Christopher Schultz ch...@christopherschultz.net 2012-04-03 22:11:01 UTC --- (In reply to comment #2) Javac failonerror defaults to true, and when it's set to true, the behavior is to try compiling everything and wait until all compile errors have happened before failing. In fact, as far as I can tell, there is actually no way to make it behave like JspC (fail after the first error). Fair enough. Perhaps a third setting to make it fail-fast (to emulate current behavior). -- Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
Re: [VOTE] Release Apache Tomcat 7.0.27
Mark, On 3/31/12 1:07 PM, Mark Thomas wrote: The proposed Apache Tomcat 7.0.27 release is now available for voting. It can be obtained from: https://dist.apache.org/repos/dist/dev/tomcat/tomcat-7/v7.0.27/ The Maven staging repo is: https://repository.apache.org/content/repositories/orgapachetomcat-132/ The svn tag is: http://svn.apache.org/repos/asf/tomcat/tc7.0.x/tags/TOMCAT_7_0_27/ The proposed 7.0.27 release is: [ ] Broken - do not release [X] Stable - go ahead and release as 7.0.27 Stable - Test system is Debian Squeeze, Java HotSpot(TM) 64-Bit Server VM (build 20.1-b02, mixed mode), OpenSSL 0.9.8o, APR 1.4.2 - MD5 sums compare - GnuPG signatures match - ZIP and tarball have same contents - Source builds properly - tcnative 1.1.23 (included) builds properly - Unit tests pass (except for tribes, which are expected to fail with no multicast support, right? See below for details) - 2 days of light use in development system (Debian Linux and Mac OS X) seem fine I had a failure in this unit test: output/build/logs/TEST-org.apache.catalina.authenticator.TestFormAuthenticator.BIO.txt:Tests run: 5, Failures: 1, Errors: 0, Time elapsed: 60.127 sec ...and before I could investigate, I inadvertently blew-away my test logs. A second run of tests did not have any errors in that test case. It's possible that I was suspending (^Z) and resuming the unit test process in such a way as to interfere with the proper execution of the test that one time. Oddly, this file has the wrong Content-Type header (text/plain) returned by the server so it doesn't render properly in a web browser: https://dist.apache.org/repos/dist/dev/tomcat/tomcat-7/v7.0.27/README.html Maybe someone could look into that. -chris PS Unit test failures in these tests: org.apache.catalina.tribes.group.interceptors.TestNonBlockingCoordinator.APR org.apache.catalina.tribes.group.interceptors.TestNonBlockingCoordinator.BIO org.apache.catalina.tribes.group.interceptors.TestNonBlockingCoordinator.NIO org.apache.catalina.tribes.group.interceptors.TestOrderInterceptor.APR org.apache.catalina.tribes.group.interceptors.TestOrderInterceptor.BIO org.apache.catalina.tribes.group.interceptors.TestOrderInterceptor.NIO org.apache.catalina.tribes.group.interceptors.TestTcpFailureDetector.APR org.apache.catalina.tribes.group.interceptors.TestTcpFailureDetector.BIO org.apache.catalina.tribes.group.interceptors.TestTcpFailureDetector.NIO org.apache.catalina.tribes.group.TestGroupChannelMemberArrival.APR org.apache.catalina.tribes.group.TestGroupChannelMemberArrival.BIO org.apache.catalina.tribes.group.TestGroupChannelMemberArrival.NIO org.apache.catalina.tribes.group.TestGroupChannelSenderConnections.APR org.apache.catalina.tribes.group.TestGroupChannelSenderConnections.BIO org.apache.catalina.tribes.group.TestGroupChannelSenderConnections.NIO org.apache.catalina.tribes.group.TestGroupChannelStartStop.APR org.apache.catalina.tribes.group.TestGroupChannelStartStop.BIO org.apache.catalina.tribes.group.TestGroupChannelStartStop.NIO signature.asc Description: OpenPGP digital signature
Re: [VOTE] Release Apache Tomcat 7.0.27
2012/4/4 Christopher Schultz ch...@christopherschultz.net: Oddly, this file has the wrong Content-Type header (text/plain) returned by the server so it doesn't render properly in a web browser: https://dist.apache.org/repos/dist/dev/tomcat/tomcat-7/v7.0.27/README.html You are just looking into repository how it is served by Subversion. It follows whether svn:mime-type is set on it, defaulting to text/plain. It is possible to do svn propset on the file, but I do not see much point. When release is published the files will be checked out into a working copy [1] and served by HTTPD from that working copy. At that time it should be served correctly. [1] http://subversion.apache.org/faq.html#website-auto-update Best regards, Konstantin Kolinko - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
[GUMP@vmgump]: Project tomcat-trunk-validate (in module tomcat-trunk) failed
To whom it may engage... This is an automated request, but not an unsolicited one. For more information please visit http://gump.apache.org/nagged.html, and/or contact the folk at gene...@gump.apache.org. Project tomcat-trunk-validate has an issue affecting its community integration. This issue affects 1 projects. The current state of this project is 'Failed', with reason 'Build Failed'. For reference only, the following projects are affected by this: - tomcat-trunk-validate : Tomcat 8.x, a web server implementing Java Servlet 3.1, ... Full details are available at: http://vmgump.apache.org/gump/public/tomcat-trunk/tomcat-trunk-validate/index.html That said, some information snippets are provided here. The following annotations (debug/informational/warning/error messages) were provided: -DEBUG- Dependency on checkstyle exists, no need to add for property checkstyle.jar. -INFO- Failed with reason build failed The following work was performed: http://vmgump.apache.org/gump/public/tomcat-trunk/tomcat-trunk-validate/gump_work/build_tomcat-trunk_tomcat-trunk-validate.html Work Name: build_tomcat-trunk_tomcat-trunk-validate (Type: Build) Work ended in a state of : Failed Elapsed: 1 sec Command Line: /usr/lib/jvm/java-6-openjdk/bin/java -Djava.awt.headless=true -Dbuild.sysclasspath=only org.apache.tools.ant.Main -Dgump.merge=/srv/gump/public/gump/work/merge.xml -Dcheckstyle.jar=/srv/gump/public/workspace/checkstyle/target/checkstyle-5.6-SNAPSHOT.jar -Dexecute.validate=true validate [Working Directory: /srv/gump/public/workspace/tomcat-trunk] CLASSPATH: /usr/lib/jvm/java-6-openjdk/lib/tools.jar:/srv/gump/public/workspace/ant/dist/lib/ant.jar:/srv/gump/public/workspace/ant/dist/lib/ant-launcher.jar:/srv/gump/public/workspace/ant/dist/lib/ant-jmf.jar:/srv/gump/public/workspace/ant/dist/lib/ant-junit.jar:/srv/gump/public/workspace/ant/dist/lib/ant-swing.jar:/srv/gump/public/workspace/ant/dist/lib/ant-apache-resolver.jar:/srv/gump/public/workspace/ant/dist/lib/ant-apache-xalan2.jar:/srv/gump/public/workspace/xml-commons/java/build/resolver.jar:/srv/gump/public/workspace/checkstyle/target/checkstyle-5.6-SNAPSHOT.jar:/srv/gump/public/workspace/apache-commons/beanutils/dist/commons-beanutils-04042012.jar:/srv/gump/public/workspace/apache-commons/cli/target/commons-cli-1.3-SNAPSHOT.jar:/srv/gump/public/workspace/apache-commons/exec/target/commons-exec-1.1.1-SNAPSHOT.jar:/srv/gump/public/workspace/apache-commons/validator/dist/commons-validator-04042012.jar:/srv/gump/public/workspace/junit/dist/junit-04042012.jar:/srv/gump /public/workspace/junit/dist/junit-dep-04042012.jar:guava-gump-31032012.jar:/srv/gump/public/workspace/apache-commons/logging/target/commons-logging-04042012.jar:/srv/gump/public/workspace/apache-commons/logging/target/commons-logging-api-04042012.jar:/srv/gump/public/workspace/commons-collections-3.x/target/commons-collections-3.3-SNAPSHOT.jar:/srv/gump/packages/antlr/antlr-3.1.3.jar:/srv/gump/public/workspace/jdom/build/jdom.jar:/srv/gump/public/workspace/velocity-engine/bin/velocity-04042012.jar:/srv/gump/public/workspace/velocity-engine/bin/velocity-04042012-dep.jar:/srv/gump/packages/javamail-1.4/mail.jar:/srv/gump/packages/javamail-1.4/lib/mailapi.jar:/srv/gump/packages/jaf-1.1ea/activation.jar - download-validate: proxyflags: setproxy: testexist: [echo] Testing for /srv/gump/public/workspace/checkstyle/target/checkstyle-5.6-SNAPSHOT.jar downloadzip: validate: [mkdir] Created dir: /srv/gump/public/workspace/tomcat-trunk/output/res/checkstyle BUILD FAILED /srv/gump/public/workspace/tomcat-trunk/build.xml:458: Could not create type checkstyle due to java.lang.NoClassDefFoundError: com/google/common/collect/Lists at com.puppycrawl.tools.checkstyle.CheckStyleTask.init(CheckStyleTask.java:78) at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57) at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) at java.lang.reflect.Constructor.newInstance(Constructor.java:532) at org.apache.tools.ant.AntTypeDefinition.innerCreateAndSet(AntTypeDefinition.java:328) at org.apache.tools.ant.AntTypeDefinition.createAndSet(AntTypeDefinition.java:274) at org.apache.tools.ant.AntTypeDefinition.icreate(AntTypeDefinition.java:219) at org.apache.tools.ant.AntTypeDefinition.create(AntTypeDefinition.java:206) at org.apache.tools.ant.ComponentHelper.createComponent(ComponentHelper.java:286) at org.apache.tools.ant.ComponentHelper.createComponent(ComponentHelper.java:264) at org.apache.tools.ant.UnknownElement.makeObject(UnknownElement.java:417) at org.apache.tools.ant.UnknownElement.maybeConfigure(UnknownElement.java:163) at
[GUMP@vmgump]: Project tomcat-tc7.0.x-validate (in module tomcat-7.0.x) failed
To whom it may engage... This is an automated request, but not an unsolicited one. For more information please visit http://gump.apache.org/nagged.html, and/or contact the folk at gene...@gump.apache.org. Project tomcat-tc7.0.x-validate has an issue affecting its community integration. This issue affects 1 projects. The current state of this project is 'Failed', with reason 'Build Failed'. For reference only, the following projects are affected by this: - tomcat-tc7.0.x-validate : Tomcat 7.x, a web server implementing Java Servlet 3.0, ... Full details are available at: http://vmgump.apache.org/gump/public/tomcat-7.0.x/tomcat-tc7.0.x-validate/index.html That said, some information snippets are provided here. The following annotations (debug/informational/warning/error messages) were provided: -DEBUG- Dependency on checkstyle exists, no need to add for property checkstyle.jar. -INFO- Failed with reason build failed The following work was performed: http://vmgump.apache.org/gump/public/tomcat-7.0.x/tomcat-tc7.0.x-validate/gump_work/build_tomcat-7.0.x_tomcat-tc7.0.x-validate.html Work Name: build_tomcat-7.0.x_tomcat-tc7.0.x-validate (Type: Build) Work ended in a state of : Failed Elapsed: 1 sec Command Line: /usr/lib/jvm/java-6-openjdk/bin/java -Djava.awt.headless=true -Dbuild.sysclasspath=only org.apache.tools.ant.Main -Dgump.merge=/srv/gump/public/gump/work/merge.xml -Dcheckstyle.jar=/srv/gump/public/workspace/checkstyle/target/checkstyle-5.6-SNAPSHOT.jar -Dexecute.validate=true validate [Working Directory: /srv/gump/public/workspace/tomcat-7.0.x] CLASSPATH: /usr/lib/jvm/java-6-openjdk/lib/tools.jar:/srv/gump/public/workspace/ant/dist/lib/ant.jar:/srv/gump/public/workspace/ant/dist/lib/ant-launcher.jar:/srv/gump/public/workspace/ant/dist/lib/ant-jmf.jar:/srv/gump/public/workspace/ant/dist/lib/ant-junit.jar:/srv/gump/public/workspace/ant/dist/lib/ant-swing.jar:/srv/gump/public/workspace/ant/dist/lib/ant-apache-resolver.jar:/srv/gump/public/workspace/ant/dist/lib/ant-apache-xalan2.jar:/srv/gump/public/workspace/xml-commons/java/build/resolver.jar:/srv/gump/public/workspace/checkstyle/target/checkstyle-5.6-SNAPSHOT.jar:/srv/gump/public/workspace/apache-commons/beanutils/dist/commons-beanutils-04042012.jar:/srv/gump/public/workspace/apache-commons/cli/target/commons-cli-1.3-SNAPSHOT.jar:/srv/gump/public/workspace/apache-commons/exec/target/commons-exec-1.1.1-SNAPSHOT.jar:/srv/gump/public/workspace/apache-commons/validator/dist/commons-validator-04042012.jar:/srv/gump/public/workspace/junit/dist/junit-04042012.jar:/srv/gump /public/workspace/junit/dist/junit-dep-04042012.jar:guava-gump-31032012.jar:/srv/gump/public/workspace/apache-commons/logging/target/commons-logging-04042012.jar:/srv/gump/public/workspace/apache-commons/logging/target/commons-logging-api-04042012.jar:/srv/gump/public/workspace/commons-collections-3.x/target/commons-collections-3.3-SNAPSHOT.jar:/srv/gump/packages/antlr/antlr-3.1.3.jar:/srv/gump/public/workspace/jdom/build/jdom.jar:/srv/gump/public/workspace/velocity-engine/bin/velocity-04042012.jar:/srv/gump/public/workspace/velocity-engine/bin/velocity-04042012-dep.jar:/srv/gump/packages/javamail-1.4/mail.jar:/srv/gump/packages/javamail-1.4/lib/mailapi.jar:/srv/gump/packages/jaf-1.1ea/activation.jar - download-validate: proxyflags: setproxy: testexist: [echo] Testing for /srv/gump/public/workspace/checkstyle/target/checkstyle-5.6-SNAPSHOT.jar downloadzip: validate: [mkdir] Created dir: /srv/gump/public/workspace/tomcat-7.0.x/output/res/checkstyle BUILD FAILED /srv/gump/public/workspace/tomcat-7.0.x/build.xml:447: Could not create type checkstyle due to java.lang.NoClassDefFoundError: com/google/common/collect/Lists at com.puppycrawl.tools.checkstyle.CheckStyleTask.init(CheckStyleTask.java:78) at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57) at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) at java.lang.reflect.Constructor.newInstance(Constructor.java:532) at org.apache.tools.ant.AntTypeDefinition.innerCreateAndSet(AntTypeDefinition.java:328) at org.apache.tools.ant.AntTypeDefinition.createAndSet(AntTypeDefinition.java:274) at org.apache.tools.ant.AntTypeDefinition.icreate(AntTypeDefinition.java:219) at org.apache.tools.ant.AntTypeDefinition.create(AntTypeDefinition.java:206) at org.apache.tools.ant.ComponentHelper.createComponent(ComponentHelper.java:286) at org.apache.tools.ant.ComponentHelper.createComponent(ComponentHelper.java:264) at org.apache.tools.ant.UnknownElement.makeObject(UnknownElement.java:417) at org.apache.tools.ant.UnknownElement.maybeConfigure(UnknownElement.java:163) at
DO NOT REPLY [Bug 51294] Since 7.0.12 do not work option unpackWARs=true for WARs outside appBase
https://issues.apache.org/bugzilla/show_bug.cgi?id=51294 Michael michael.sonnleit...@gmail.com changed: What|Removed |Added CC||michael.sonnleitner@gmail.c ||om -- Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
DO NOT REPLY [Bug 48550] Update examples and default server.xml to use UTF-8
https://issues.apache.org/bugzilla/show_bug.cgi?id=48550 Michael michael.sonnleit...@gmail.com changed: What|Removed |Added CC||michael.sonnleitner@gmail.c ||om -- Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
DO NOT REPLY [Bug 52858] High CPU load in the NIO connector, when a client breaks connection unexpectedly
https://issues.apache.org/bugzilla/show_bug.cgi?id=52858 Michael michael.sonnleit...@gmail.com changed: What|Removed |Added CC||michael.sonnleitner@gmail.c ||om -- Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
[GUMP@vmgump]: Project tomcat-tc7.0.x-test (in module tomcat-7.0.x) failed
To whom it may engage... This is an automated request, but not an unsolicited one. For more information please visit http://gump.apache.org/nagged.html, and/or contact the folk at gene...@gump.apache.org. Project tomcat-tc7.0.x-test has an issue affecting its community integration. This issue affects 1 projects, and has been outstanding for 4 runs. The current state of this project is 'Failed', with reason 'Build Failed'. For reference only, the following projects are affected by this: - tomcat-tc7.0.x-test : Tomcat 7.x, a web server implementing Java Servlet 3.0, ... Full details are available at: http://vmgump.apache.org/gump/public/tomcat-7.0.x/tomcat-tc7.0.x-test/index.html That said, some information snippets are provided here. The following annotations (debug/informational/warning/error messages) were provided: -DEBUG- Dependency on tomcat-tc7.0.x-dbcp exists, no need to add for property tomcat-dbcp-src.jar. -DEBUG- Dependency on commons-daemon exists, no need to add for property commons-daemon.native.src.tgz. -DEBUG- Dependency on commons-daemon exists, no need to add for property tomcat-native.tar.gz. -DEBUG- Dependency on tomcat-tc7.0.x-dbcp exists, no need to add for property tomcat-dbcp.home. -INFO- Failed with reason build failed -INFO- Project Reports in: /srv/gump/public/workspace/tomcat-7.0.x/output/build/logs The following work was performed: http://vmgump.apache.org/gump/public/tomcat-7.0.x/tomcat-tc7.0.x-test/gump_work/build_tomcat-7.0.x_tomcat-tc7.0.x-test.html Work Name: build_tomcat-7.0.x_tomcat-tc7.0.x-test (Type: Build) Work ended in a state of : Failed Elapsed: 22 mins 7 secs Command Line: /usr/lib/jvm/java-6-openjdk/bin/java -Djava.awt.headless=true -Dbuild.sysclasspath=only org.apache.tools.ant.Main -Dgump.merge=/srv/gump/public/gump/work/merge.xml -Djunit.jar=/srv/gump/public/workspace/junit/dist/junit-04042012.jar -Dcommons-daemon.native.src.tgz=/srv/gump/public/workspace/apache-commons/daemon/dist/bin/commons-daemon-04042012-native-src.tar.gz -Dtomcat-native.tar.gz=/srv/gump/public/workspace/apache-commons/daemon/dist/bin/commons-daemon-04042012-native-src.tar.gz -Dexamples.sources.skip=true -Dtomcat-dbcp.home=/srv/gump/public/workspace/tomcat-7.0.x/tomcat-deps -Djdt.jar=/srv/gump/packages/eclipse/plugins/org.eclipse.jdt.core_3.4.2/jdtcore.jar -Dcommons-daemon.jar=/srv/gump/public/workspace/apache-commons/daemon/dist/commons-daemon-04042012.jar -Dtomcat-dbcp-src.jar=/srv/gump/public/workspace/tomcat-7.0.x/tomcat-deps/tomcat-dbcp-src.jar -Dtest.accesslog=true -Dcommons-pool.home=/srv/gump/public/workspace/commons-pool-1.x -Dcommons-dbcp.home=/ srv/gump/public/workspace/commons-dbcp-1.x -Dtomcat-dbcp.jar=/srv/gump/public/workspace/tomcat-7.0.x/tomcat-deps/tomcat-dbcp-04042012.jar test [Working Directory: /srv/gump/public/workspace/tomcat-7.0.x] CLASSPATH: /usr/lib/jvm/java-6-openjdk/lib/tools.jar:/srv/gump/public/workspace/tomcat-7.0.x/output/build/webapps/examples/WEB-INF/classes:/srv/gump/public/workspace/tomcat-7.0.x/output/testclasses:/srv/gump/public/workspace/ant/dist/lib/ant.jar:/srv/gump/public/workspace/ant/dist/lib/ant-launcher.jar:/srv/gump/public/workspace/ant/dist/lib/ant-jmf.jar:/srv/gump/public/workspace/ant/dist/lib/ant-junit.jar:/srv/gump/public/workspace/ant/dist/lib/ant-swing.jar:/srv/gump/public/workspace/ant/dist/lib/ant-apache-resolver.jar:/srv/gump/public/workspace/ant/dist/lib/ant-apache-xalan2.jar:/srv/gump/public/workspace/xml-commons/java/build/resolver.jar:/srv/gump/public/workspace/tomcat-7.0.x/output/build/bin/bootstrap.jar:/srv/gump/public/workspace/tomcat-7.0.x/output/build/bin/tomcat-juli.jar:/srv/gump/public/workspace/tomcat-7.0.x/output/build/lib/annotations-api.jar:/srv/gump/public/workspace/tomcat-7.0.x/output/build/lib/servlet-api.jar:/srv/gump/public/workspace/tomcat-7.0.x/outp ut/build/lib/jsp-api.jar:/srv/gump/public/workspace/tomcat-7.0.x/output/build/lib/el-api.jar:/srv/gump/public/workspace/tomcat-7.0.x/output/build/lib/catalina.jar:/srv/gump/public/workspace/tomcat-7.0.x/output/build/lib/catalina-ant.jar:/srv/gump/public/workspace/tomcat-7.0.x/output/build/lib/tomcat-coyote.jar:/srv/gump/public/workspace/tomcat-7.0.x/output/build/lib/jasper.jar:/srv/gump/public/workspace/tomcat-7.0.x/output/build/lib/jasper-el.jar:/srv/gump/public/workspace/tomcat-7.0.x/output/build/lib/catalina-tribes.jar:/srv/gump/public/workspace/tomcat-7.0.x/output/build/lib/catalina-ha.jar:/srv/gump/public/workspace/tomcat-7.0.x/output/build/lib/tomcat-api.jar:/srv/gump/public/workspace/tomcat-7.0.x/output/build/lib/tomcat-util.jar:/srv/gump/packages/javamail-1.4/mail.jar:/srv/gump/packages/javamail-1.4/lib/mailapi.jar:/srv/gump/packages/jaf-1.1ea/activation.jar:/srv/gump/packages/eclipse/plugins/org.eclipse.jdt.core_3.4.2/jdtcore.jar:/srv/gump/public/workspace/tomcat-7.
[GUMP@vmgump]: Project tomcat-trunk-test (in module tomcat-trunk) failed
To whom it may engage... This is an automated request, but not an unsolicited one. For more information please visit http://gump.apache.org/nagged.html, and/or contact the folk at gene...@gump.apache.org. Project tomcat-trunk-test has an issue affecting its community integration. This issue affects 1 projects, and has been outstanding for 4 runs. The current state of this project is 'Failed', with reason 'Build Failed'. For reference only, the following projects are affected by this: - tomcat-trunk-test : Tomcat 8.x, a web server implementing Java Servlet 3.1, ... Full details are available at: http://vmgump.apache.org/gump/public/tomcat-trunk/tomcat-trunk-test/index.html That said, some information snippets are provided here. The following annotations (debug/informational/warning/error messages) were provided: -DEBUG- Dependency on tomcat-trunk-dbcp exists, no need to add for property tomcat-dbcp-src.jar. -DEBUG- Dependency on commons-daemon exists, no need to add for property commons-daemon.native.src.tgz. -DEBUG- Dependency on commons-daemon exists, no need to add for property tomcat-native.tar.gz. -DEBUG- Dependency on tomcat-trunk-dbcp exists, no need to add for property tomcat-dbcp.home. -INFO- Failed with reason build failed -INFO- Project Reports in: /srv/gump/public/workspace/tomcat-trunk/output/build/logs The following work was performed: http://vmgump.apache.org/gump/public/tomcat-trunk/tomcat-trunk-test/gump_work/build_tomcat-trunk_tomcat-trunk-test.html Work Name: build_tomcat-trunk_tomcat-trunk-test (Type: Build) Work ended in a state of : Failed Elapsed: 22 mins 46 secs Command Line: /usr/lib/jvm/java-6-openjdk/bin/java -Djava.awt.headless=true -Dbuild.sysclasspath=only org.apache.tools.ant.Main -Dgump.merge=/srv/gump/public/gump/work/merge.xml -Djunit.jar=/srv/gump/public/workspace/junit/dist/junit-04042012.jar -Dcommons-daemon.native.src.tgz=/srv/gump/public/workspace/apache-commons/daemon/dist/bin/commons-daemon-04042012-native-src.tar.gz -Dtomcat-native.tar.gz=/srv/gump/public/workspace/apache-commons/daemon/dist/bin/commons-daemon-04042012-native-src.tar.gz -Dexamples.sources.skip=true -Dtomcat-dbcp.home=/srv/gump/public/workspace/tomcat-trunk/tomcat-deps -Djdt.jar=/srv/gump/packages/eclipse/plugins/org.eclipse.jdt.core_3.4.2/jdtcore.jar -Dcommons-daemon.jar=/srv/gump/public/workspace/apache-commons/daemon/dist/commons-daemon-04042012.jar -Dtomcat-dbcp-src.jar=/srv/gump/public/workspace/tomcat-trunk/tomcat-deps/tomcat-dbcp-src.jar -Dtest.accesslog=true -Dcommons-pool.home=/srv/gump/public/workspace/commons-pool-1.x -Dcommons-dbcp.home=/ srv/gump/public/workspace/commons-dbcp-1.x -Dtomcat-dbcp.jar=/srv/gump/public/workspace/tomcat-trunk/tomcat-deps/tomcat-dbcp-04042012.jar test [Working Directory: /srv/gump/public/workspace/tomcat-trunk] CLASSPATH: /usr/lib/jvm/java-6-openjdk/lib/tools.jar:/srv/gump/public/workspace/tomcat-trunk/output/build/webapps/examples/WEB-INF/classes:/srv/gump/public/workspace/tomcat-trunk/output/testclasses:/srv/gump/public/workspace/ant/dist/lib/ant.jar:/srv/gump/public/workspace/ant/dist/lib/ant-launcher.jar:/srv/gump/public/workspace/ant/dist/lib/ant-jmf.jar:/srv/gump/public/workspace/ant/dist/lib/ant-junit.jar:/srv/gump/public/workspace/ant/dist/lib/ant-swing.jar:/srv/gump/public/workspace/ant/dist/lib/ant-apache-resolver.jar:/srv/gump/public/workspace/ant/dist/lib/ant-apache-xalan2.jar:/srv/gump/public/workspace/xml-commons/java/build/resolver.jar:/srv/gump/public/workspace/tomcat-trunk/output/build/bin/bootstrap.jar:/srv/gump/public/workspace/tomcat-trunk/output/build/bin/tomcat-juli.jar:/srv/gump/public/workspace/tomcat-trunk/output/build/lib/annotations-api.jar:/srv/gump/public/workspace/tomcat-trunk/output/build/lib/servlet-api.jar:/srv/gump/public/workspace/tomcat-trunk/outp ut/build/lib/jsp-api.jar:/srv/gump/public/workspace/tomcat-trunk/output/build/lib/el-api.jar:/srv/gump/public/workspace/tomcat-trunk/output/build/lib/catalina.jar:/srv/gump/public/workspace/tomcat-trunk/output/build/lib/catalina-ant.jar:/srv/gump/public/workspace/tomcat-trunk/output/build/lib/tomcat-coyote.jar:/srv/gump/public/workspace/tomcat-trunk/output/build/lib/jasper.jar:/srv/gump/public/workspace/tomcat-trunk/output/build/lib/jasper-el.jar:/srv/gump/public/workspace/tomcat-trunk/output/build/lib/catalina-tribes.jar:/srv/gump/public/workspace/tomcat-trunk/output/build/lib/catalina-ha.jar:/srv/gump/public/workspace/tomcat-trunk/output/build/lib/tomcat-api.jar:/srv/gump/public/workspace/tomcat-trunk/output/build/lib/tomcat-jni.jar:/srv/gump/public/workspace/tomcat-trunk/output/build/lib/tomcat-util.jar:/srv/gump/packages/javamail-1.4/mail.jar:/srv/gump/packages/javamail-1.4/lib/mailapi.jar:/srv/gump/packages/jaf-1.1ea/activation.jar:/srv/gump/packages/eclipse/plugins/org
