On 24.09.10 17:04, Jacob Kjome wrote:
Since Log4j must support JDK1.4 (actually, still 1.3, I believe), I
don't see how we could use JDK1.5+ ThreadLocal.remove()?
That said, there are other ways of cleaning up ThreadLocals that don't
require remove(). For examples, see CrazyBob's "Hard Core Jav
On 24.09.2010, at 17:04, Jacob Kjome wrote:
> Since Log4j must support JDK1.4 (actually, still 1.3, I believe), I don't see
> how we could use JDK1.5+ ThreadLocal.remove()?
I suspected something like this...I was actually surprised to see that there's
still development activity here.
What I see
Since Log4j must support JDK1.4 (actually, still 1.3, I believe), I don't see
how we could use JDK1.5+ ThreadLocal.remove()?
That said, there are other ways of cleaning up ThreadLocals that don't require
remove(). For examples, see CrazyBob's "Hard Core Java: ThreadLocal" from
back in 2006 [1
The initial problem description was sent to the users list:
http://www.mail-archive.com/log4j-u...@logging.apache.org/msg11921.html
However, I think it actually belongs here...
I believe that the MDC should provide a method that internally calls
ThreadLocal#remove which was added to the API wi
