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 22:10:41 GMT
https://issues.apache.org/bugzilla/show_bug.cgi?id=50486

--- Comment #12 from marcel@frightanic.com 2012-01-25 22:10:41 UTC ---
Ok, the patch was accepted, modified and applied I get that.
a) Shouldn't this ticket be marked as 'resolved'?
b) What's the ETA for 1.2.17?

Also, I believe there's a second issue. The way it's implemented right know
clients must explicitly call MDC.clear(). Couldn't/shouldn't remove() call
clear() internally once the last item was removed()?
How do clients know when to call clear()? In a request processing chain (e.g.
Servlet filter) several parties may write items and each one of them is
responsible to call remove() for the items it added. On the way it items are
added, on the way out they're removed in reverse order. And the last guy closes
the door i.e. calls clear(). However, how does a client know that he's the
last?

-- 
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


Mime
View raw message