DO NOT REPLY [Bug 53022] session is expired/removed/not found by unknown reason
https://issues.apache.org/bugzilla/show_bug.cgi?id=53022 Mark Thomas changed: What|Removed |Added Status|NEW |RESOLVED Resolution||INVALID --- Comment #3 from Mark Thomas 2012-04-02 08:18:22 UTC --- There is no evidence here of a bug with Tomcat. Expecting the committers to review every change since 7.0.23 on the basis of this bug report is - frankly - ridiculous. Please follow up this issue on the users mailing list. There are two things I strongly recommend that you do before posting there: 1. Check the logs for errors. 2. Add the requested session ID to the access log and review the access logs. -- 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 51606] Version 1.2.32 does not work with Jenkins on RHEL 6
https://issues.apache.org/bugzilla/show_bug.cgi?id=51606 Rene Snajder changed: What|Removed |Added Resolution|INVALID |FIXED --- Comment #4 from Rene Snajder 2012-04-02 09:53:52 UTC --- Just an update: It seems to work in 1.2.35 (without me changing ANY config). So I guess someone did find the bug and fixed it. Thank you. -- 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 53024] New: Accessing Servlet while Reloading context gives 404 error
https://issues.apache.org/bugzilla/show_bug.cgi?id=53024 Bug #: 53024 Summary: Accessing Servlet while Reloading context gives 404 error Product: Tomcat 7 Version: unspecified Platform: PC Status: NEW Severity: normal Priority: P2 Component: Catalina AssignedTo: dev@tomcat.apache.org ReportedBy: yours...@freemail.hu Classification: Unclassified I think the following Tomcat 6 bug is reoccuring in Tomcat 7.0.26: https://issues.apache.org/bugzilla/show_bug.cgi?id=43683 -- 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 52135] Global error page is not handled
https://issues.apache.org/bugzilla/show_bug.cgi?id=52135 --- Comment #10 from Filip Hanik 2012-04-02 14:36:55 UTC --- Mark, I agree with your assessment. It is an enhancement, and a useful one. The spec itself is, and will remain, fairly limited on feature set, and as Tomcat evolves nothing prevents us from adding usability to the container. -- 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 "elimorgan" by elimorgan
Dear Wiki user, You have subscribed to a wiki page or wiki category on "Tomcat Wiki" for change notification. The "elimorgan" page has been changed by elimorgan: http://wiki.apache.org/tomcat/elimorgan New page: Why is it important muscular fitness When we talk about muscular fitness, the majority of people consider fit body, muscle advancement for your sole purpose of constructing muscle. It really is definitely good that individuals understand that the conversion of fat to muscle is a necessity within our society, since the typical body excess fat percentage is also large and gaining this for a healthier, drop some weight and work out. So as outlined by this philosophy can reach the two an increase in muscle mass and shed weight. excellent increasingly serious excess weight reduction program or exercise takes this into account. Having said that, in regards to muscle fitness you will find many other aspects than just healthier philosophy will not be even described over. To compensate, I will take a closer search on the muscular fitness within this article and to present some facets of wellbeing that seem to overlook. Widespread facets of Muscle Fitness Commonly when individuals think about [[http://www.muscleandfitness.net | muscle and fitness]] center on cosmetic look. This is the "physical contest 'more typically perceived that most of the people love. There is practically nothing wrong with such enthusiasm, but is somewhat restricted in scope however. That is, you can find a lot of practical goals muscle fitness could be attained, as well as cosmetics. Do you would like power? silly query. Naturally I do. Just because a person is solid does not imply that that person actually is robust. In order to strengthen the force, we now have to operate on a series of exercise routines that raise muscle function. isolation exercise routines like leg lifts and related workout routines will do practically nothing with regards to force majeure. Squats heavy weight for lower reps time period, even so, grow your power. Muscle Fitness What to complete with rehabilitation? Because the lifting of legs had been negatively chosen within the past area, it is actually essential to mention the proper role of leg raises. While you can find many makes use of for the isolation workout routines like leg raises, that are normally made use of for your rehabilitation of injuries. As a result, an physical exercise as strengthen leg increase a knee injury. muscular endurance and Fitness Individuals that have had - and has no (?) - understand that - dependant upon his fitness - sooner or later you receive a feeling of tiredness within the legs or arms. Every muscle features a muscular endurance. For muscle tissues are nicely skilled this potential is substantial and untrained muscle tissues is low. So what comes about when you practical experience muscle fatigue is the fact that they have reached their limits of endurance. Nicely skilled persons participating in sports activities like rowing, muscle fatigue may be expert really promptly. There is a solution to eradicate fatigue this kind of but you should make a series of repetitive exercises high body weight and increase them enormously. Let us keep with the example rower, his process would most likely be repeated push a sizable amount of times. What comes about then is that the muscles on the shoulders, arms and chest is enhanced resilience. Note however, do distinctive exercise routines for muscle groups will not suggest that the workout routines from your negligence of other muscle groups. For muscle fitness you should train all your muscle tissues. - 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. 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 52 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-02042012.jar -Dcommons-daemon.native.src.tgz=/srv/gump/public/workspace/apache-commons/daemon/dist/bin/commons-daemon-02042012-native-src.tar.gz -Dtomcat-native.tar.gz=/srv/gump/public/workspace/apache-commons/daemon/dist/bin/commons-daemon-02042012-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-02042012.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-02042012.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. 0.x/tomcat-deps/tomcat-dbcp-02042012.jar:/srv/gump/public/workspace/apache-commons/daemon/dist/commons-daemon-02042012.jar:/srv/gump/public/workspace/junit/dist/
[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: 21 mins 56 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-02042012.jar -Dcommons-daemon.native.src.tgz=/srv/gump/public/workspace/apache-commons/daemon/dist/bin/commons-daemon-02042012-native-src.tar.gz -Dtomcat-native.tar.gz=/srv/gump/public/workspace/apache-commons/daemon/dist/bin/commons-daemon-02042012-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-02042012.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-02042012.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-02042012.jar:/srv/gump/public/workspace/apache-commons/daemon/dist/commons-da
[Tomcat Wiki] Update of "LocalBadContent" by ChuckCaldarale
Dear Wiki user, You have subscribed to a wiki page or wiki category on "Tomcat Wiki" for change notification. The "LocalBadContent" page has been changed by ChuckCaldarale: http://wiki.apache.org/tomcat/LocalBadContent?action=diff&rev1=43&rev2=44 Comment: spam removal masterjin\.com mathsolutions\.50webs\.com mnsp\.cn + muscleandfitness\.net myeurowatches\.com mystreyguy nekoo\.cn - 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
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. Mark - 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 Sandra Madden changed: What|Removed |Added Version|unspecified |6.0.26 OS/Version|All |Windows 7 -- 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 Sandra Madden changed: What|Removed |Added OS/Version||Windows 7 -- 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
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. Mark - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
DO NOT REPLY [Bug 53022] session is expired/removed/not found by unknown reason
https://issues.apache.org/bugzilla/show_bug.cgi?id=53022
Leonardo Uribe changed:
What|Removed |Added
Status|RESOLVED|REOPENED
Resolution|INVALID |
--- Comment #4 from Leonardo Uribe 2012-04-02 20:41:44 UTC
---
Ok, I'll explain it in deep. Look this code in
org.apache.catalina.session.ManagerBase
protected String generateSessionId() {
String result = null;
do {
if (result != null) {
// Not thread-safe but if one of multiple increments is lost
// that is not a big deal since the fact that there was any
// duplicate is a much bigger issue.
duplicates++;
}
result = sessionIdGenerator.generateSessionId();
} while (sessions.containsKey(result));
return result;
}
But the in tomcat 7.0.23 was
protected synchronized String generateSessionId() {
..
The code was changed in 7.0.26 from use just one SecureRandom to:
private Queue randoms = new
ConcurrentLinkedQueue();
There is one good reason for use a synchronized method in that part. Before
Java 7, there is no mention anywere on java spec that SecureRandom is thread
safe. To ensure thread safety, SecureRandom and the algorithm should ensure
thread safety (look than in 7.0.26, the algorihm can be configured, are you
100% sure the algorithm selected will be thread safe?). Being strict with java
spec, you should use a synchronized block in that part.
But the worst part is the use of a queue of SecureRandom instances and the way
the algorithm check for duplicates. Since the containsKey() operation and the
further put() operation occur in different places (see ManagerBase.add()),
there is no warrant a duplicate sessionid cannot be included in the time
between containsKey() and put() and since you have multiple SecureRandom
instances this risk is even more evident.
Even if the probability that those events could happen is very, very, very
small, it is clear that ManagerBase.add() operation should do the check for
duplicates too and if that so, try to generate and alternate identifier.
Note how tricky is all this. Reproduce this failure is something almost
impossible, one in a million. There is no unit test that could catch it, but
the bug exists, it is theorically feasible.
After investigating my particular problem, I found that my problem was more
related with JMeter. In my load test I used the default Java for HTTP protocol
implementation (because is a little bit faster) but since there is no control
over connection reuse, Tomcat throw SocketException after some time without log
it in the default logger. Switching to HttpClient4 solves the problem.
It is curious how many users has been caught over the time into the same
problem (JMeter-Tomcat). After all, the solution is not trivial.
Please be more kind in the future. By experience I know that sometimes gather
evidence about these kind of bugs is very difficult, so don't throw away such
reports, without consider them first.
--
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 #1 from Christopher Schultz 2012-04-02 21:20:00 UTC --- +1 to the idea, but I'd like to see an implementation that is more in line with similar tasks like and : they use "failOnError" (defaults to 'true' to get current behavior) and "errorProperty". If you set failOnError=false and errorProperty=jasperFailed, then you can test for jasperFailed and emit any kind of warning/error you'd like from your ant target. -- 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: Improving Ant Task for JSP Compilation
Nick, On 3/31/12 4:34 PM, Nick Williams wrote: > This morning I filed issues 53011 and 53012, about general improvements to > the Ant task used for compiling JSPs. These two issues are rather important > to our team, and are making using the compiler rather difficult. In the > interest of both improving Tomcat and meeting our needs as quickly as > possible, I am interested in possibly contributing code changes to effect > these improvements, and possible others. Great! > I read the information at http://tomcat.apache.org/getinvolved.html and > related links, and understand that my first step is building Tomcat and my > second is proposing patches to the other developers (presumably by > attaching them to the issues I filed). If I'm missing anything so far, > please let me know. That sounds like a good start. Remember that everything you do should be in Tomcat's 'trunk'. Here's the svn root for that: http://svn.apache.org/repos/asf/tomcat/trunk All patches should be against trunk (they'll get back-ported to 7.0.x and possibly 6.0.x). > What I'd really like is a little further guidance about this particular > feature in Tomcat. Who is really familiar with it that I can ask questions > of if I don't understand something I see? Perhaps the best thing to do is look at the svn history for the files involved. Start with org.apache.jasper.JspC and the related files like Compiler, etc. to see who has updated them recently. Mostly, it's best to ask questions on this list and let anyone answer them who can, rather than trying to directly contact any one person. > What do the developers on the list think about the ideas proposed in > these two issues? > > Bug 53011 - Ant Jasper task fails after one error +1 - seems reasonable. I've added some comments to the bug. > Bug 53012 - Ant Jasper task does not name including file when > included file has compile error +1 also seems reasonable. Check the current behavior of the trunk to make sure this isn't already in there. > I believe they > make Tomcat better, but that's just because they meet our immediate needs. That's host these projects grow: patches are always welcome. Basically anything that doesn't a) violate the servlet specification or b) significantly impact performance or c) require sweeping changes to the code is fair game. Thanks, -chris signature.asc Description: OpenPGP digital signature
DO NOT REPLY [Bug 53022] session is expired/removed/not found by unknown reason
https://issues.apache.org/bugzilla/show_bug.cgi?id=53022
Mark Thomas changed:
What|Removed |Added
Status|REOPENED|RESOLVED
Resolution||INVALID
--- Comment #5 from Mark Thomas 2012-04-02 21:25:31 UTC ---
(In reply to comment #4)
> Ok, I'll explain it in deep. Look this code in
> org.apache.catalina.session.ManagerBase
>
> protected String generateSessionId() {
>
> String result = null;
>
> do {
> if (result != null) {
> // Not thread-safe but if one of multiple increments is lost
> // that is not a big deal since the fact that there was any
> // duplicate is a much bigger issue.
> duplicates++;
> }
>
> result = sessionIdGenerator.generateSessionId();
>
> } while (sessions.containsKey(result));
>
> return result;
> }
>
> But the in tomcat 7.0.23 was
>
> protected synchronized String generateSessionId() {
> ..
No it wasn't. The code quoted for 7.0.23 is incorrect. The only code changes to
ManagerBase since 7.0.23 are to add some comments and to make some fields
final.
> The code was changed in 7.0.26 from use just one SecureRandom to:
>
> private Queue randoms = new
> ConcurrentLinkedQueue();
Wrong again. That change was introduced in 7.0.5.
> There is one good reason for use a synchronized method in that part. Before
> Java 7, there is no mention anywere on java spec that SecureRandom is thread
> safe. To ensure thread safety, SecureRandom and the algorithm should ensure
> thread safety (look than in 7.0.26, the algorihm can be configured, are you
> 100% sure the algorithm selected will be thread safe?). Being strict with java
> spec, you should use a synchronized block in that part.
Wrong again. There is no concurrent access to SecureRandom instances.
> But the worst part is the use of a queue of SecureRandom instances and the way
> the algorithm check for duplicates. Since the containsKey() operation and the
> further put() operation occur in different places (see ManagerBase.add()),
> there is no warrant a duplicate sessionid cannot be included in the time
> between containsKey() and put() and since you have multiple SecureRandom
> instances this risk is even more evident.
I agree the duplicate check is incomplete but I believe it to be completely
unnecessary. The odds of getting a duplicate are so astronomically small that I
do not believe we should even bother checking. That code is a left over from
very early days of Tomcat when insecure random number generators were used that
did have a realistic chance of generating a duplicate.
> Even if the probability that those events could happen is very, very, very
> small, it is clear that ManagerBase.add() operation should do the check for
> duplicates too and if that so, try to generate and alternate identifier.
As I stated above, I disagree. The check is pointless.
> Note how tricky is all this. Reproduce this failure is something almost
> impossible, one in a million. There is no unit test that could catch it, but
> the bug exists, it is theorically feasible.
The odds are an awful lot longer than that.
> After investigating my particular problem, I found that my problem was more
> related with JMeter. In my load test I used the default Java for HTTP protocol
> implementation (because is a little bit faster) but since there is no control
> over connection reuse, Tomcat throw SocketException after some time without
> log
> it in the default logger. Switching to HttpClient4 solves the problem.
Which just confirms my point that this was not a Tomcat bug at all. Depending
on what triggered the exception, it may well be logged below INFO level and
therefore not be logged by default.
> It is curious how many users has been caught over the time into the same
> problem (JMeter-Tomcat). After all, the solution is not trivial.
>
> Please be more kind in the future. By experience I know that sometimes gather
> evidence about these kind of bugs is very difficult, so don't throw away such
> reports, without consider them first.
The 'kindness' of a response is largely proportional to the quality of the bug
report. Lets take a look at your initial report:
- Tomcat version provided? Yes.
- Test case to reproduce provided? No.
- Description of how to reproduce? No.
- Configuration details for Tomcat (Connector, changes to defaults, etc.)
provided? No.
- Configuration for JMeter provided? No.
- Chances of anyone being able to recreate the problem you were seeing? Zero.
- Chances of anyone being able to make an educated guess as to the cause of the
problem you were seeing? Zero.
- Evidence of further research on your part to reduce search space (e.g.
testing with 7.0.25) ? None.
Overall, a fairly useless bug repo
svn commit: r1308581 - in /tomcat/site/trunk: docs/resources.html xdocs/resources.xml
Author: markt Date: Mon Apr 2 21:32:12 2012 New Revision: 1308581 URL: http://svn.apache.org/viewvc?rev=1308581&view=rev Log: Add a new book. Modified: tomcat/site/trunk/docs/resources.html tomcat/site/trunk/xdocs/resources.xml Modified: tomcat/site/trunk/docs/resources.html URL: http://svn.apache.org/viewvc/tomcat/site/trunk/docs/resources.html?rev=1308581&r1=1308580&r2=1308581&view=diff == --- tomcat/site/trunk/docs/resources.html (original) +++ tomcat/site/trunk/docs/resources.html Mon Apr 2 21:32:12 2012 @@ -280,6 +280,14 @@ +http://www.packtpub.com/apache-tomcat-7-essentials-building-middleware-servers/book?utm_source=tomcat.apache.org&utm_medium=link&utm_content=pod&utm_campaign=mdb_002136"; rel="nofollow">Apache Tomcat 7 Essentials, by Tanuj Khare + +Packt Publishing (03/2012) + + + + + http://www.packtpub.com/tomcat-6-developers-guide/book?utm_source=tomcat.apache.org&utm_medium=link&utm_content=pod&utm_campaign=mdb_002136"; rel="nofollow">Tomcat 6 Developer's Guide, by Damodar Chetty Packt Publishing (12/2009) Modified: tomcat/site/trunk/xdocs/resources.xml URL: http://svn.apache.org/viewvc/tomcat/site/trunk/xdocs/resources.xml?rev=1308581&r1=1308580&r2=1308581&view=diff == --- tomcat/site/trunk/xdocs/resources.xml (original) +++ tomcat/site/trunk/xdocs/resources.xml Mon Apr 2 21:32:12 2012 @@ -52,6 +52,10 @@ + http://www.packtpub.com/apache-tomcat-7-essentials-building-middleware-servers/book?utm_source=tomcat.apache.org&utm_medium=link&utm_content=pod&utm_campaign=mdb_002136"; rel="nofollow">Apache Tomcat 7 Essentials, by Tanuj Khare + Packt Publishing (03/2012) + + http://www.packtpub.com/tomcat-6-developers-guide/book?utm_source=tomcat.apache.org&utm_medium=link&utm_content=pod&utm_campaign=mdb_002136"; rel="nofollow">Tomcat 6 Developer's Guide, by Damodar Chetty Packt Publishing (12/2009) - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
Re: svn commit: r1308581 - in /tomcat/site/trunk: docs/resources.html xdocs/resources.xml
2012/4/3 : > Author: markt > Date: Mon Apr 2 21:32:12 2012 > New Revision: 1308581 > > URL: http://svn.apache.org/viewvc?rev=1308581&view=rev > Log: > Add a new book. > > Modified: > tomcat/site/trunk/docs/resources.html > tomcat/site/trunk/xdocs/resources.xml There is also this page: https://wiki.apache.org/tomcat/Tomcat/Books It is essentially the same list as on tomcat.apache.org. > + href="http://www.packtpub.com/apache-tomcat-7-essentials-building-middleware-servers/book?utm_source=tomcat.apache.org&utm_medium=link&utm_content=pod&utm_campaign=mdb_002136"; > rel="nofollow">Apache Tomcat 7 Essentials, by Tanuj Khare > + Packt Publishing (03/2012) Best regards, Konstantin Kolinko - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
DO NOT REPLY [Bug 53022] session is expired/removed/not found by unknown reason
https://issues.apache.org/bugzilla/show_bug.cgi?id=53022 Leonardo Uribe changed: What|Removed |Added Resolution|INVALID |WONTFIX --- Comment #6 from Leonardo Uribe 2012-04-02 22:06:05 UTC --- I would thought and algorithm so critical like session id generation would be bullet proof anyway . not very professional maybe too lazy to do it right ... whatever I checked the comparison and it seems my IDE confused tomcat sources with other ones taken from a optional dependency, so I was looking an old version. Thanks for notice it. Finally, it is clear this issue should be solved as Won't Fix, instead Invalid. After all, the path taken here is ignore a possible failure because its probability is very small. I appreciate your help and your fast response with this issue ;-) calm down! be cool!. -- 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 53022] session is expired/removed/not found by unknown reason
https://issues.apache.org/bugzilla/show_bug.cgi?id=53022 Mark Thomas changed: What|Removed |Added Resolution|WONTFIX |INVALID -- 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
+1 Tested maven artifacts with the plugin. And I have tested applications. 2012/3/31 Mark Thomas : > 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 > [ ] Stable - go ahead and release as 7.0.27 Stable > > Cheers, > > Mark > > - > To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org > For additional commands, e-mail: dev-h...@tomcat.apache.org > -- Olivier Lamy Talend: http://coders.talend.com http://twitter.com/olamy | http://linkedin.com/in/olamy - 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 #2 from Raja 2012-04-02 23:14:34 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. Is there a traction on this? Would it help if we submit a patch? -- 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 Raja changed: What|Removed |Added CC||rtr...@gmail.com -- 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 53022] session is expired/removed/not found by unknown reason
https://issues.apache.org/bugzilla/show_bug.cgi?id=53022 --- Comment #7 from Leonardo Uribe 2012-04-03 02:20:59 UTC --- After evaluating the probabilities, it seems to be the size of the key is critical. Since by default sessionIdLength is 16, there are 2^128 = 3.4e38 possible combinations. So, the possible number of sessions in a single tomcat instance and the ammount of request a tomcat instance is capable to handle in a reasonable frame of time is much more less. The duplicate check is useless, because it will not affect significantly the probability, but a single lookup over a ConcurrentHashMap is cheap enough to let it (because the duplicate should happen in a even shorter frame of time). Anyway, a simple check taking the value returned by put() operation, could easily detect the occurrence, and it is not necessary to do anything more than restore the old session in the map, and throw an exception for the new one. It will be enough to prevent the duplicate session effect at 100% and they are just some few lines of code. Other different history will happen if the user reduce sessionIdLength, but there is nothing to do in that case, maybe a check for a minimal sessionIdLength is reasonable, but it is questionable because usually you want that key be large enough to make computationally infeasible to find it by brute force. -- 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 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. 0.x/tomcat-deps/tomcat-dbcp-03042012.jar:/srv/gump/public/workspace/apache-commons/daemon/dist/commons-daemon-03042012.jar:
[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 .eclipse.jdt.core_3.4.2/jdtcore.jar:/srv/gump/public/workspace/tomcat-trunk/tomcat-deps/tomcat-dbcp-03042012.jar:/srv/gump/public/workspace
