Get MDC keys from LoggingEvent

Hi, Is there a way to retrieve a collection of MDC keys from a LoggingEvent? If not, then could one be added? We currently log all details except MDC to file for later analysis and plan to start using MDC; though this isn't going to be of great use unless we can capture all the MDC content

AsyncAppender issues

There are a couple of open issues with the log4j AsyncAppender, specifically: http://issues.apache.org/bugzilla/show_bug.cgi?id=26224 http://issues.apache.org/bugzilla/show_bug.cgi?id=28006 http://issues.apache.org/bugzilla/show_bug.cgi?id=38137 I've reviewed the bug reports and the code in qu

Re: [POLL] Base JDK version support for log4j 1.3?

Good evening, David J. M. Karlsen wrote: Some of the vendors are behind - WebSphere v6 (latest available) is at JDK1.3. I really don't see any reason to make the l4j 1.4 target - if it does - we'll have some problems - and probably leave l4j for good. WebSphere v5.0 was at JDK 1.3 WebSphere

Re: [POLL] Base JDK version support for log4j 1.3?

Hola, > Some of the vendors are behind - WebSphere v6 (latest available) is at > JDK1.3. I don't think so. Even later versions of WebSphere 5.x support JDK 1.4. See for example: http://www.websphere-world.com/modules.php?name=News&file=article&sid=1164. The argument for supporting older JDKs i

Re: [POLL] Base JDK version support for log4j 1.3?

Andreas Fester wrote: Mark Womack wrote: We have talked about this before, and I plan to poll the user list, but I thought we could talk about it some more here first. What base JDK version do we want to support for log4j 1.3? > JDK 1.2? > JDK 1.3? I do not see any reason to support

DO NOT REPLY [Bug 37349] - DBAppender not working with jTDS driver

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bu