logging-log4j-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 50486] Memoryleak - org.apache.log4j.helpers.ThreadLocalMap
Date Wed, 25 Jan 2012 17:23:23 GMT

--- Comment #9 from f.bantner@axon-e.de 2012-01-25 17:23:23 UTC ---
I'm monitoring this report for quiet some time now and I don't understand the
problem why it is not fixed.

This is one of the major sources of memory leaks in tomcat which bugges every
developer for quiet some time now.

The fix would be something like a 3-liner and is a complete no-brainer: simply
call the remove method via reflections if it exists. 

So here is the "patch":

try {
  ThreadLocalMap.class.getMethod( "remove" ).invoke( tlm );
} catch( NoSuchMethodException e ){
  // Do nothing

This won't fix the bug for the 1.4 people but for the 90% of the rest of us
which aren't bound to old problems anyway.

So please please fix this.

Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-dev-help@logging.apache.org

View raw message