-----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-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). > > The ThreadLocal issues were: > - Commons Lang https://issues.apache.org/jira/browse/LANG-586 > - Spring Batch (I don't have a reference) > > The commons logging issue was an open JAR file: > - https://issues.apache.org/bugzilla/show_bug.cgi?id=47465 Thanks for the reference. I was looking for a change in commons-logging and just couldn't find it. We are using commons-lang 2.3 in our previously-mentioned Cocoon project that is giving us warnings when we shut it down. Fortunately for us, we have had a policy of always bouncing the JVM when we redeploy webapps, so it's never been a "real" problem. Always good to make sure things are running as smooth as possible, though. - -chris -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAkz0FsQACgkQ9CaO5/Lv0PCoJACcDayShH2SjTJWDrx8h5Boqe1F 2MQAoLzDAPHL1VLkBcwpS2IAk5NQZG3z =kkve -----END PGP SIGNATURE----- --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
