On Fri, 24 Feb 2006, Jess Holle wrote: | | Unless, of course, requiring 1.4 means one can assume a better ThreadLocal and | use it more freely, for instance. [I know ThreadLocal improved over the | various JVM releases, but I don't know whether those improvements went back | into old JVM's maintenance releases.]
The new (fast) ThreadLocal has been around since 1.4, iiuc. However, using actual ThreadLocal objects has as far as I understand always been better than "doing it yourself" as log4j does, since it is supposed to clean up after itself - and it magically improves for each java version, while synched-maps really don't (see NDC). Here's the "threadlocal leaks plug" once more (it's interesting): http://www.jroller.com/page/tackline?entry=fixing_threadlocal Sun bug db entry by, I assume, the same guy ("tackline"): http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6254531 (vote for it - it hurts all webapp developers!) Regards, Endre. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
