DO NOT REPLY [Bug 53138] New: Not able to download a file size of 740KB using NIO connector in tomcat version 7.0.27. But with the same configuration I was able to download that in tomcat 7.0.26.
https://issues.apache.org/bugzilla/show_bug.cgi?id=53138 Bug #: 53138 Summary: Not able to download a file size of 740KB using NIO connector in tomcat version 7.0.27. But with the same configuration I was able to download that in tomcat 7.0.26. Product: Tomcat 7 Version: 7.0.27 Platform: PC Status: NEW Severity: blocker Priority: P2 Component: Connectors AssignedTo: dev@tomcat.apache.org ReportedBy: cpra...@gmail.com Classification: Unclassified We have an application that uses a java script file of size around 700Kb that will be downloaded as part of the client. The connector used was NIO . All these days we did not see any issue till Tomcat 7.0.26. When we upgraded it to the latest Tomcat version 7.0.27 we started getting this problem. The file is never getting downloaded the connection will be broken in middle. And we used fiddler to see what is happening and it gives us a message as below “Content-Length mismatch: Response Header indicated 757,692 bytes, but server sent 262,142 bytes.” If I use the default connector there is no issues. it works fine. To reproduce this we have created a sample application. Please follow the steps below. Clean up all the browser cash: 1.Deploy TestNIOConnector app in tomcat. 2.In server.xml change to connect to NIO as shown below. 3.Start the service and try to access this file using the following URL in IE. http://localhost:9880/TestNIOConnector/apidocs.js -- 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 53138] Not able to download a file size of 740KB using NIO connector in tomcat version 7.0.27. But with the same configuration I was able to download that in tomcat 7.0.26.
https://issues.apache.org/bugzilla/show_bug.cgi?id=53138 --- Comment #1 from prakash 2012-04-24 12:01:29 UTC --- Created attachment 28666 --> https://issues.apache.org/bugzilla/attachment.cgi?id=28666 Sample app to reproduce this issue This app is to reproduce the issue. -- 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 50864] Reconfigure pool on the fly using JMX
https://issues.apache.org/bugzilla/show_bug.cgi?id=50864 --- Comment #5 from RobertPattinson 2012-04-24 12:41:10 UTC --- We also ran into this issue recently. For example, it would be very useful to increase max size of the pool without restarting the server. http://www.quora.com/iPhone-4s-Cases http://www.quora.com/iPhone-4-Cases-iPhone-4S-Cases http://www.quora.com/iPhone-Accessories -- 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 53139] New: Prevent showing keystore/truststore passwords via JMX in cleartext (with solution)
https://issues.apache.org/bugzilla/show_bug.cgi?id=53139 Bug #: 53139 Summary: Prevent showing keystore/truststore passwords via JMX in cleartext (with solution) Product: Tomcat 7 Version: 7.0.27 Platform: PC OS/Version: Linux Status: NEW Severity: normal Priority: P2 Component: Catalina AssignedTo: dev@tomcat.apache.org ReportedBy: randy.very.g...@gmail.com Classification: Unclassified Created attachment 28667 --> https://issues.apache.org/bugzilla/attachment.cgi?id=28667 JConsole view of a freshly installed Tomcat 7, with SSL enabled in server.xml Issue: I've noticed that Tomcat 7.0.27 exposes the keystore and truststore passwords via JMX in cleartext (in the bean JIoEndpoint). This was not the case in Tomcat 6, for example the JIoEndpoint bean which was exposed had much fewer attributes. I have specified the passwords as attributes in the HTTPS connector tag in server.xml. Solution: My quick solution was to add mbeans-descriptors.xml to the package org.apache.tomcat.util.net (where JIOEndpoint lies) with this content: With this, no attributes from JIoEndpoint are exposed anymore. A better solution would be to add a more meaningful mbeans-descriptors.xml, only filtering out critical keystore/truststore information. Also see here: http://www.mail-archive.com/users@tomcat.apache.org/msg98216.html Thanks -- 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
[Tomcat Wiki] Update of "FAQ/Miscellaneous" by BaruchAtta
Dear Wiki user, You have subscribed to a wiki page or wiki category on "Tomcat Wiki" for change notification. The "FAQ/Miscellaneous" page has been changed by BaruchAtta: http://wiki.apache.org/tomcat/FAQ/Miscellaneous?action=diff&rev1=29&rev2=30 1. [[#Q27|What order do webapps start (or How can I change startup order)?]] 1. [[#Q28|What's the different between a Valve and Filter?]] 1. [[#Q29|How do I set system properties at startup?]] + 1. [[#Q30|How do I translate to English from Tomcateese?]] == Answers == @@ -358, +359 @@ Windows service users - use [[http://web.bvu.edu/staff/david/tcservcfg/|this]] + <> + + <>'''How do I translate to English from Tomcateese?''' + + more to come! [[CategoryFAQ|CategoryFAQ]] - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
[Tomcat Wiki] Update of "FAQ/Miscellaneous" by BaruchAtta
Dear Wiki user, You have subscribed to a wiki page or wiki category on "Tomcat Wiki" for change notification. The "FAQ/Miscellaneous" page has been changed by BaruchAtta: http://wiki.apache.org/tomcat/FAQ/Miscellaneous?action=diff&rev1=30&rev2=31 <>'''How do I translate to English from Tomcateese?''' + Sometimes it is hard to understand the documentation that is supposed to be easy to understand. For example: + + In order to be executed, a web application must be deployed on a servlet container. + + Translated means: + In order to run your web application, you must move or copy the files and folders that make up your web app to a folder that is referred to as "servlet container". Now good luck in finding that folder. + + - more to come! + OK, more to come! [[CategoryFAQ|CategoryFAQ]] - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
[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. 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 6 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-24042012.jar -Dcommons-daemon.native.src.tgz=/srv/gump/public/workspace/apache-commons/daemon/dist/bin/commons-daemon-24042012-native-src.tar.gz -Dtomcat-native.tar.gz=/srv/gump/public/workspace/apache-commons/daemon/dist/bin/commons-daemon-24042012-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-24042012.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-24042012.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 .eclipse.jdt.core_3.4.2/jdtcore.jar:/srv/gump/public/workspace/tomcat-trunk/tomcat-deps/tomcat-dbcp-24042012.jar:/srv/gump/public/workspace/apache-commons/daemon/dist/commons-dae
[Tomcat Wiki] Update of "FAQ/Miscellaneous" by markt
Dear Wiki user, You have subscribed to a wiki page or wiki category on "Tomcat Wiki" for change notification. The "FAQ/Miscellaneous" page has been changed by markt: http://wiki.apache.org/tomcat/FAQ/Miscellaneous?action=diff&rev1=31&rev2=32 Comment: Not an FAQ, not helpful and not particularly funny. 1. [[#Q27|What order do webapps start (or How can I change startup order)?]] 1. [[#Q28|What's the different between a Valve and Filter?]] 1. [[#Q29|How do I set system properties at startup?]] - 1. [[#Q30|How do I translate to English from Tomcateese?]] == Answers == @@ -358, +357 @@ Windows service users - use [[http://web.bvu.edu/staff/david/tcservcfg/|this]] - - <> - - <>'''How do I translate to English from Tomcateese?''' - - Sometimes it is hard to understand the documentation that is supposed to be easy to understand. For example: - - In order to be executed, a web application must be deployed on a servlet container. - - Translated means: - In order to run your web application, you must move or copy the files and folders that make up your web app to a folder that is referred to as "servlet container". Now good luck in finding that folder. - - - OK, more to come! [[CategoryFAQ|CategoryFAQ]] - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
Re: svn commit: r1303339 - in /tomcat/tc7.0.x/trunk: ./ java/org/apache/catalina/realm/RealmBase.java webapps/docs/changelog.xml
Sorry I haven't been able to quote the details of this commit made by markt a month ago, but I didn't keep a copy in my inbox. I previously submitted an enhancement to the corresponding test suite https://issues.apache.org/bugzilla/show_bug.cgi?id=53096 I fully expected all my test cases would succeed against mark's trivial bugfix. I recently brought my trunk sandbox up to svn: r1329909 and was puzzled to discover the relevant test case still FAILED! I've done a lot of digging and debugging, and come to the conclusion this problem is more subtle than originally thought. Does anyone know whether the current fix has been validated against a real android device? I suspect it doesn't work. The issues are: 1. the one line change: -String md5a1 = getDigest(username, realm); +// In digest auth, digests are always lower case +String md5a1 = getDigest(username, realm).toLowerCase(Locale.ENGLISH); If I remember correctly, the intention was to be make tomcat more tolerant of clients that presented digest strings with upper case hexadecimal digits provided they were otherwise correct. The change in r1329909 seems to me as if it does nothing of relevance to that objective. 2. Client digest responses require an outer hash which will wrap one or two inner hashes... /if/ the inner hashes are (incorrectly) represented with upper case hex digits, then the outer hash will inevitably be different to the (correct situation) where they are represented with lower case hex digits. This difference is independent of whether the HTTP Digest header delivers its hashes using lower or upper case hex digits. 3. I have reworked the TestDigestAuthenticator class to explore these alternatives. I have also drafted a change to RealmBase that "fixes" situation 1 above, but it still fails with both cases of situation 2. 4. My suspicion is that /if/ the android digest algorithm (incorrectly) uses upper case hex digits with its outer hashes, it will probably also do the same with its inner hashes. If I am right, the two failing tests in situation 3 will not work until RealmBase has even more compensatory logic. I can explain and explore this in more detail, but I need a strategic decision first: do we back out the change and go to wontfix (i.e. wont be tolerant), or do we proceed with trying to be flexible? There must be a lot of androids out there carrying the "non standard" DIGEST logic (whatever that might really be). Regards, Brian - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
Re: svn commit: r1303339 - in /tomcat/tc7.0.x/trunk: ./ java/org/apache/catalina/realm/RealmBase.java webapps/docs/changelog.xml
On 24/04/2012 20:51, Brian Burch wrote: > Sorry I haven't been able to quote the details of this commit made by > markt a month ago, but I didn't keep a copy in my inbox. > > I previously submitted an enhancement to the corresponding test suite > https://issues.apache.org/bugzilla/show_bug.cgi?id=53096 > I fully expected all my test cases would succeed against mark's trivial > bugfix. > > I recently brought my trunk sandbox up to svn: r1329909 and was puzzled > to discover the relevant test case still FAILED! > > I've done a lot of digging and debugging, and come to the conclusion > this problem is more subtle than originally thought. Does anyone know > whether the current fix has been validated against a real android > device? I suspect it doesn't work. I certainly didn't at the time, but I can quite easily. > The issues are: > > 1. the one line change: > -String md5a1 = getDigest(username, realm); > +// In digest auth, digests are always lower case > +String md5a1 = getDigest(username, > realm).toLowerCase(Locale.ENGLISH); > > If I remember correctly, the intention was to be make tomcat more > tolerant of clients that presented digest strings with upper case > hexadecimal digits provided they were otherwise correct. The change in > r1329909 seems to me as if it does nothing of relevance to that objective. Agreed. > 2. Client digest responses require an outer hash which will wrap one or > two inner hashes... /if/ the inner hashes are (incorrectly) represented > with upper case hex digits, then the outer hash will inevitably be > different to the (correct situation) where they are represented with > lower case hex digits. This difference is independent of whether the > HTTP Digest header delivers its hashes using lower or upper case hex > digits. > > 3. I have reworked the TestDigestAuthenticator class to explore these > alternatives. I have also drafted a change to RealmBase that "fixes" > situation 1 above, but it still fails with both cases of situation 2. > > 4. My suspicion is that /if/ the android digest algorithm (incorrectly) > uses upper case hex digits with its outer hashes, it will probably also > do the same with its inner hashes. If I am right, the two failing tests > in situation 3 will not work until RealmBase has even more compensatory > logic. > > I can explain and explore this in more detail, but I need a strategic > decision first: do we back out the change and go to wontfix (i.e. wont > be tolerant), or do we proceed with trying to be flexible? There must be > a lot of androids out there carrying the "non standard" DIGEST logic > (whatever that might really be). Let me see what happens with 2.3.5 and 4.0.3 and decide then. Watch this space... Mark - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
Re: svn commit: r1303339 - in /tomcat/tc7.0.x/trunk: ./ java/org/apache/catalina/realm/RealmBase.java webapps/docs/changelog.xml
On 24/04/2012 21:11, Mark Thomas wrote: > On 24/04/2012 20:51, Brian Burch wrote: >> Sorry I haven't been able to quote the details of this commit made by >> markt a month ago, but I didn't keep a copy in my inbox. >> >> I previously submitted an enhancement to the corresponding test suite >> https://issues.apache.org/bugzilla/show_bug.cgi?id=53096 >> I fully expected all my test cases would succeed against mark's trivial >> bugfix. >> >> I recently brought my trunk sandbox up to svn: r1329909 and was puzzled >> to discover the relevant test case still FAILED! >> >> I've done a lot of digging and debugging, and come to the conclusion >> this problem is more subtle than originally thought. Does anyone know >> whether the current fix has been validated against a real android >> device? I suspect it doesn't work. > > I certainly didn't at the time, but I can quite easily. > >> The issues are: >> >> 1. the one line change: >> -String md5a1 = getDigest(username, realm); >> +// In digest auth, digests are always lower case >> +String md5a1 = getDigest(username, >> realm).toLowerCase(Locale.ENGLISH); >> >> If I remember correctly, the intention was to be make tomcat more >> tolerant of clients that presented digest strings with upper case >> hexadecimal digits provided they were otherwise correct. The change in >> r1329909 seems to me as if it does nothing of relevance to that objective. > > Agreed. (if that was the objective). However, that was not the objective. The objective was to handle programs that created hashes for the user database that used capitals. The Android DIGEST auth issue was related to URIs. See https://issues.apache.org/bugzilla/show_bug.cgi?id=52954 > Let me see what happens with 2.3.5 and 4.0.3 and decide then. > > Watch this space... BZ 52954 is not an issue in Android 4.0.3 but it is in 2.3.5. Given that 2.3.x is by far the most prevalent Android version at the moment we should certainly take a look at fixing BZ 52954. Upper/lower case digests from android clients is a red herring. Mark - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
DO NOT REPLY [Bug 52744] [Jasper] JSP files are always recompiled in development mode
https://issues.apache.org/bugzilla/show_bug.cgi?id=52744 Mark Thomas changed: What|Removed |Added Status|NEEDINFO|RESOLVED Resolution||INVALID --- Comment #13 from Mark Thomas 2012-04-24 20:52:06 UTC --- If the problem is reproducible in Geronimo but not Tomcat then it is a Geronimo problem, not a Tomcat one. I'd be happy to look at this as a Tomcat issue if a test case can be provided that demonstrates the problem on Tomcat. -- 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 53057] Add OpenSSL version number to INFO log message when initializing
https://issues.apache.org/bugzilla/show_bug.cgi?id=53057 Mark Thomas changed: What|Removed |Added Status|NEW |RESOLVED Resolution||FIXED --- Comment #1 from Mark Thomas 2012-04-24 20:54:56 UTC --- Changelog says this is fixed. -- 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 16 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 14 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-25042012.jar -Dcommons-daemon.native.src.tgz=/srv/gump/public/workspace/apache-commons/daemon/dist/bin/commons-daemon-25042012-native-src.tar.gz -Dtomcat-native.tar.gz=/srv/gump/public/workspace/apache-commons/daemon/dist/bin/commons-daemon-25042012-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-25042012.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-25042012.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/eclipse/plugins/org.eclipse.jdt.core_3.4.2/jdtcore.jar:/srv/gump/public/workspace/tomcat-7.0.x/tomcat-deps/tomcat-dbcp-25042012.jar:/srv/gump/public/workspace/apache-commons/daemon/dist/commons-daemon-25042012.jar:/srv/gump/ public/workspace/junit/dist/junit-25042012.jar - [junit] Apr 25, 2012 4:45:
[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: 23 mins 21 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-25042012.jar -Dcommons-daemon.native.src.tgz=/srv/gump/public/workspace/apache-commons/daemon/dist/bin/commons-daemon-25042012-native-src.tar.gz -Dtomcat-native.tar.gz=/srv/gump/public/workspace/apache-commons/daemon/dist/bin/commons-daemon-25042012-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-25042012.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-25042012.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 .eclipse.jdt.core_3.4.2/jdtcore.jar:/srv/gump/public/workspace/tomcat-trunk/tomcat-deps/tomcat-dbcp-25042012.jar:/srv/gump/public/workspace
