> If you set the cachingAllowed attribute on your <Context> element to > "false", will this meet your needs? I believe this will disable caching > and therefore eliminate the memory concerns you have.
Thanks for the reply. Our situation was actually reversed. We are using Tomcat with a custom classloader that dynamically determines the jars to load at startup, but otherwise defers to Tomcat for class loading functionality. However, we found a bottleneck in our code where the ClassLoader was loading the same resource over and over again. We finally realized that Tomcat would not cache this resource when the jars were dynamically added instead of being present in web-inf. We have implemented our own caching but before doing so, wanted to find out about the Tomcat experience so we avoided any pitfalls that are already well-known. Also, I am not sure we are talking about the same resources here. We were concerned with the ClassLoader.getResource() method that loads resources into the JVM. I would imagine the Context element refers to resources serverd up by the web server, such as static HTML, JPGs, etc. -- View this message in context: http://www.nabble.com/Are-ClassLoader-resources-cached-forever--tp25440666p25864704.html Sent from the Tomcat - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
