[LOG4J2-937] log4j to log4j2 ThreadContext (MDC)

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Cannot Reproduce
• Affects Version/s: 2.1
• Component/s: API, Core, Log4j 1.2 bridge

Environment

tested on Windows XP and 7

• Assignee: Ralph Goers
• Reporter: CEM DAYANIK
• Created: 14/Jan/15 09:59
• Updated: 18/Jun/19 04:51
• Resolved: 18/Jun/19 04:51

Description

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.