[ https://issues.apache.org/jira/browse/LOG4J2-937?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ralph Goers resolved LOG4J2-937. -------------------------------- Resolution: Cannot Reproduce Closing due to lack of response from reporter. > log4j to log4j2 ThreadContext (MDC) > ----------------------------------- > > Key: LOG4J2-937 > URL: https://issues.apache.org/jira/browse/LOG4J2-937 > Project: Log4j 2 > Issue Type: Bug > Components: API, Core, log4j 1.2 emulation > Affects Versions: 2.1 > Environment: tested on Windows XP and 7 > Reporter: CEM DAYANIK > Assignee: Ralph Goers > Priority: Major > > We are using slf4j and log4j2. Also a third party library using log4j via its > config file, so we have added log4j to log4j2 adaptor. > While using MDC or directly ThreadContext, 3.party library logs (which is > using log4j) doesnt pick up "context key" and directed to default route. > 3.party library have a loggerfactory class name in its config file. > Loggerfactory implementation is pretty straight forward, it creates a logger > from repository. (log4j) > I have written another class, creates the logger from LoggerFactory (log4j2) > and change 3.party properties file. Everything works fine in this case. > So it seems the problem isnt about 3.party library but log4j to log4j2 > adaptor. -- This message was sent by Atlassian JIRA (v7.6.3#76005)