https://issues.apache.org/bugzilla/show_bug.cgi?id=57274
--- Comment #1 from Phillip <pverhey...@broadleafcommerce.com> --- I think that this issue can be closed. The problems that I highlighted below are a necessary outcome of Tomcat needing to scan for ServletContainerInitializers in the web application. It does this by looping through all of the classes in all of the jars loaded by the application and reading them in with a FileInputStream. I would imagine that it is a performance improvement to, after loading a class via FileInputStream, to go ahead and load the superclass and interfaces into the cache as well. However, the superclass has to be loaded through the WebappClassLoader which is what causes a problem in my case. After doing some additional digging (specifically at http://java.net/jira/browse/SERVLET_SPEC-36), I found that I can disable the jar scanning completely by adding an empty <absolute-ordering /> in my web.xml. After testing this everything in my application works as I would expect. Sorry for the false positive here but hopefully someone else will come across this research and will save them some debugging time. Also, I would also like to take this opportunity to say thanks for all the contributors to Tomcat! We love the simplicity and performance, and we consistently recommend Tomcat as our #1 servlet container for those that use Broadleaf. Thanks again! -- 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
