<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=Content-Type content="text/html; charset=us-ascii">
<META content="MSHTML 6.00.2900.2873" name=GENERATOR></HEAD>
<BODY>
<DIV><SPAN class=303490915-25052006><FONT face=Arial size=2>I recall a recent
thread in which someone pointed out that Tomcat gradually took up more and more
memory on each each restart of a webapp running within it.</FONT></SPAN></DIV>
<DIV><SPAN class=303490915-25052006><FONT face=Arial
size=2></FONT></SPAN> </DIV>
<DIV><SPAN class=303490915-25052006><FONT face=Arial size=2>I wonder if the
fault lies in using Jakarta Commons Logging (JCL) libraries prior to
v1.1? See <A
href="http://jakarta.apache.org/commons/logging/guide.html#Classloader_and_Memory_Management">http://jakarta.apache.org/commons/logging/guide.html#Classloader_and_Memory_Management</A> for
a discussion in which it's made clear that for versions prior to 1.1, classes
which call LogFactory.getLog(...) must also call LogFactory.release(), or risk
having references to loaded classes held on to by the logging
framework.</FONT></SPAN></DIV>
<DIV><SPAN class=303490915-25052006><FONT face=Arial
size=2></FONT></SPAN> </DIV>
<DIV><SPAN class=303490915-25052006><FONT face=Arial size=2>Offhand, I don't
know which version of JCL is distributed with 6.0.4 and 6.2.1, but if you're
suffering from Tomcat memory leaks you could do worse than try upgrading to JCL
1.1.</FONT></SPAN></DIV>
<DIV><SPAN class=303490915-25052006><FONT face=Arial
size=2></FONT></SPAN> </DIV>
<DIV><SPAN class=303490915-25052006><FONT face=Arial
size=2>Jon</FONT></SPAN></DIV>
<DIV><SPAN class=303490915-25052006><FONT face=Arial
size=2></FONT></SPAN> </DIV></BODY></HTML>