Tomcat Memory Leak: classLoader never released

[Vanessa Bensemhoun <vb...@calendra.com>]

All,
I've seen a problem with a Tomcat Memory Leak which seems to be similar with the bug 20758 http://nagoya.apache.org/bugzilla/show_bug.cgi?id=20758 but I would like to be sure about that... 
I have several J2EE applications hosted by my Tomcat 4.1.24 and the problem is when I deploy 3 or 4 applications, I have an OutOfMemory error (until now, it seems to be a known problem from Tomcat). Moreover, the same thing occurs if I only start, stop and restart an application several times using the Tomcat Manager. 
To resume, if I play too much time with my applications, the OutOfMemory error occurs... 

Using OptimizeIt, I tried to understand the problem and I found that my application ClassLoader was never totally released when I stop my application. There are always some strange references on it and especially the "classLoader of java.security.ProtectionDomain", which comes from the org.apache.catalina.core.StandardContext.start() method. (I tried the same thing with a very simple application (servlet which bind a RMI service), with the same result)
Do you think it could be the same problem than described in the bug report described above? Or maybe a "side-effect"? 
Do someone have any ideas? Is there a workaround to avoid to wait for the Tomcat 5.0?
Thanks,
Vanessa.



---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-dev-help@jakarta.apache.org