[slf4j-dev] [Bug 266] Memory Leak: Clearing MDC context with Log4J

[Matthew Bishop]

Marcel, is there an associated Pull Request at GitHub?



From: "bugzilla-daemon at qos.ch<mailto:bugzilla-daemon at qos.ch>" <bugzilla-daemon at qos.ch<mailto:bugzilla-daemon at qos.ch>>
Reply-To: slf4j developers list <slf4j-dev at qos.ch<mailto:slf4j-dev at qos.ch>>
Date: Thursday, September 25, 2014 at 2:29 AM
To: "slf4j-dev at qos.ch<mailto:slf4j-dev at qos.ch>" <slf4j-dev at qos.ch<mailto:slf4j-dev at qos.ch>>
Subject: [slf4j-dev] [Bug 266] Memory Leak: Clearing MDC context with Log4J

Marcel<mailto:marcel at frightanic.com>changed bug 266<http://bugzilla.slf4j.org/show_bug.cgi?id=266>
What    Removed Added
CC              marcel at frightanic.com<mailto:marcel at frightanic.com>

Comment # 1<http://bugzilla.slf4j.org/show_bug.cgi?id=266#c1> on bug 266<http://bugzilla.slf4j.org/show_bug.cgi?id=266> from Marcel<mailto:marcel at frightanic.com>

No feedback in more than 2 years? Isn't this considered important? Even though
we use slf4j throughout the entire code base we still have to use the log4j MDC
directly due to this bug.

________________________________
You are receiving this mail because:

  *   You are the assignee for the bug.

[http://elasticpath.com/images/ep.gif]
Matthew Bishop, Senior Architect
Mobile: +1-604-218-8102
Email: Matthew.Bishop at elasticpath.com<mailto:Matthew.Bishop at elasticpath.com>

Elastic Path Software Inc.
Web elasticpath.com <http://www.elasticpath.com/> | Blog getelastic.com <http://www.getelastic.com/> | Twitter twitter.com/elasticpath <http://www.twitter.com/elasticpath>
Careers elasticpath.com/jobs<http://www.elasticpath.com/jobs> | Community grep.elasticpath.com <http://grep.elasticpath.com/>

Confidentiality Notice: This message is intended only for the use of the designated addressee(s), and may contain information that is privileged, confidential and exempt from disclosure. Any unauthorized viewing, disclosure, copying, distribution or use of information contained in this e-mail is prohibited and may be unlawful. If you received this e-mail in error, please reply to the sender immediately to inform us you are not the intended recipient and delete the email from your computer system.



-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.qos.ch/pipermail/slf4j-dev/attachments/20140925/224cd5ee/attachment.html>