Mark > 2. Why would Tomcat be cleaning up the WebappLoader instance everytime > successfully but seems to 'hang-on' to the WebappClassLoader instance? My money is on it being JVM code rather than Tomcat code that is hanging onto the WebappClassLoader. Are you testing with JDK 1.6.0_15 or later by any chance?
Yes. I'm using Apple's JVM and Suns (on Ubuntu 9.04) I traced the webappclassloader gcroot. It appears to be connected via sun.awt.AppContext? Any thoughts. Gerwood ________________________________________ From: Mark Thomas [ma...@apache.org] Sent: Tuesday, 10 November 2009 9:07 AM To: Tomcat Users List Subject: Re: WebappClassLoader and undeploy Gerwood Stewart wrote: > Tomact seems to have retained 1 on the WebappClassLoader instances. > > I have two questions at this point: > > 1. From the Javadocs both WebappClassLoader and WebappLoader are class > loaders. What are the differences and why does Tomcat use both? WebappClassLoader is the actual class loader, WebappLoader is the context level object that manages the class loader. > 2. Why would Tomcat be cleaning up the WebappLoader instance everytime > successfully but seems to 'hang-on' to the WebappClassLoader instance? My money is on it being JVM code rather than Tomcat code that is hanging onto the WebappClassLoader. Are you testing with JDK 1.6.0_15 or later by any chance? Mark --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
