DO NOT REPLY [Bug 14042] - Memory leaks with JBoss 3.x +(Tomcat/Jetty)

[bu...@apache.org]

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=14042>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=14042

Memory leaks with JBoss 3.x +(Tomcat/Jetty)





------- Additional Comments From craig.mcclanahan@sun.com  2002-12-18 07:38 -------
I tried your test against stand-alone Tomcat 4.1.17 (just released for general
availability), using the manager reload command to initiate the reloads, and
observed basically the same behavior.  I suspect you may be correct about static
resources being maintained for things like LogFactory (Tomcat ships with
commons-logging-api in the common/lib directory).

As an experiment, I've added a method to LogFactory that lets you clear the
LogFactory instance (and associated Log instances) for a single class loader,
and then modified ActionServlet.destroy() to call this method.  Memory still
went up -- but at a slightly lower pace -- but I still eventually ran out.  As
such, I'm pretty suspicious that this is really a container problem, but this
needs more investigation.

--
To unsubscribe, e-mail:   <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>