https://issues.apache.org/bugzilla/show_bug.cgi?id=51276
--- Comment #7 from Mark Thomas <ma...@apache.org> 2011-05-30 08:55:57 UTC --- Your test cases are not representative of the typical jar handling within Tomcat. As is explained in the code commentary in the patch, Jars in web applications are referenced via JNDI URLs. Using JarFile with these URLs (or any non-file URL) triggers the creation of a full copy of the jar file in the temp directory. This is significantly slower than accessing the jar with JarInputStream. The issue you are seeing is as a result of using shared jars. While supported, such an approach is not recommended due to the complications it can create both when upgrading and with memory leaks on reload with some libraries. The shared jars are referenced via file URLs so the switch to JarInputStream will result in a slow down in that case. As per comment #4, I'll see if there is an easy way to switch to JarFile for jars referenced via file URLs rather than JNDI URLs -- 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
