I don't have a solution for you, but I've noticed this as well. Actually, in most cases, after I do "install" and "remove", most of my jars are freed up except for Log4j.jar. I've even tried setting up a ServletContextListener and upon contextDestroyed, I call "LogManager.shutdown()" which should make sure that Log4j no longer has any existing threads running. However, Tomcat still holds onto the Log4j.jar resource.
Any ideas on how to solve this would be very much appreciated! Jake At 03:02 PM 7/11/2002 -0500, you wrote: >Hello, > >I'm noticing a peculiar behavior of Tomcat 4.0.4: After undeploying a >webapp, I cannot remove the libs that were part of the webapp (inside >the webapps/myapp/WEB-INF/lib folder). For example, I deployed my lib >using the http://.../manager/install URI and deployed it from a >directory rather than a WAR: > >http://localhost:8080/manager/install?path=/test&war=file:c:/dev/webapp > >Inside of this folder there exist serveral jars: > >C:/dev/webapp/WEB-INF/lib/log.jar >C:/dev/webapp/WEB-INF/lib/log4j.jar >...etc. > >Once the webapp is deploy, used, and then undeployed, I cannot remove >these libs. I would like to remove them because I am updating the libs >as part of my development and need to redeploy my webapp with the newer >jars. > >Has anyone else noticed this? If so, is this a bug or a limitation of >classloading (and unloading) of Java? If not, could there be something >I'm doing wrong on my server? > >Thanks in advance, > >Jason > >-- >To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> >For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
