-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Mark,
On 11/29/2010 12:37 PM, Mark Thomas wrote:
> On 29/11/2010 17:29, Christopher Schultz wrote:
>> All,
>>
>> At some point, someone (markt?) mentioned that, as a result of Tomcat's
>> memory leak detection capabilities, either log4j or commons-log
On 29/11/2010 17:37, Mark Thomas wrote:
> The commons logging issue was an open JAR file:
Doh. I meant log4j.
Mark
-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.a
On 29/11/2010 17:29, Christopher Schultz wrote:
> All,
>
> At some point, someone (markt?) mentioned that, as a result of Tomcat's
> memory leak detection capabilities, either log4j or commons-logging (or
> both) had fixed at least one ThreadLocal issue.
>
> I was wondering if someone could post
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
All,
At some point, someone (markt?) mentioned that, as a result of Tomcat's
memory leak detection capabilities, either log4j or commons-logging (or
both) had fixed at least one ThreadLocal issue.
I was wondering if someone could post a reference for
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
All,
At some point, someone (markt?) mentioned that, as a result of Tomcat's
memory leak detection capabilities, either log4j or commons-logging (or
both) had fixed at least one ThreadLocal issue.
I was wondering if someone could post a reference for
