https://issues.apache.org/bugzilla/show_bug.cgi?id=50486
--- Comment #56 from Patric Rufflar <[email protected]> --- >Or do I miss something? I suppose you are. I'll let some details out but I hope that this helps nevertheless: The problem is that a ThreadLocal is always implicitly strongly referenced by the thread which it's tied to (until the thread dies). Because most application servers used thread pools the thread will most probably remain alive. As a result, a reference to the ThreadLocal is still kept. If the ThreadLocal references an object of the web application, the web application classloader can also not be garbage collected and most of the memory of the (already shut down) application cannot be freed. This is exactly the reason why tomcats memory leak detection mechanism is correctly issuing the warning (which this bug report is about). -- You are receiving this mail because: You are the assignee for the bug. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
