We are using 4.1.20 where this particular leak (and another one in
Jasper) is supposed to be fixed and we use jikes in any case.
Thanks,
Adi
> On Fri, 14 Mar 2003 10:51:57 +0530, "Uddhav Shirname" <[EMAIL PROTECTED]> said:
> The release note of Tomcat 4.1.18 talks about a known memory leak
> with
Just to followup, we have found a few things that were causing this
leak, two that were particular to our setup, but the third seems to be
a Tomcat problem (4.1.20 with Jasper2):
1) log4j was eating up a lot of memory and there was a slow leak. Since
it wasn't strictly required, we've stopped usin
