tomcat-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Christopher Schultz <>
Subject Re: Tomcat 4.0.x memory leak (not javac)
Date Tue, 02 Dec 2003 14:11:27 GMT


Uhhh... this looks like "standard operating procedure" for Java to me...

When you dump a ClassLoader and all of it's object get GC'd, the VM 
almost never GC's the "unused" classes. The new ClassLoader re-loads all 
those classes, again, and you get "new" "versions" of those classes 
loaded into the VM. Even if there are no more instances of those 
classes, I thought they stuck around...

I was not suprised by anything mentioned in that bug. The only thing 
that's a shame is the fact that it's true, and it does interfere with 
the ability of an app server to re-load contexts indefinately. :(

The -Xnoclassgc option still exists for the 1.4.1 VM, so maybe I'm 
completely wrong, here. :)


To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message