[OT] ThreadLocal fixes in log4j|commons-logging

[Christopher Schultz <ch...@christopherschultz.net>]

-----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 that: either a
bugzilla/JIRA entry somewhere or a version number where I could inspect
the change log(s).

Thanks in advance to anyone who can refer me to this information.

- -chris
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAkzz4mIACgkQ9CaO5/Lv0PBSnQCfcuBG7k+hve8qURh3+pqSwiZR
Os0AnAi1HKYCaJ89Ot/Kh1rCmTi2zR4A
=RFxZ
-----END PGP SIGNATURE-----

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