[LOG4J2-1180] Logger cache does not account for message factory

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.4.1
• Fix Version/s: 2.5, 2.6.1
• Component/s: API
• Assignee: Gary D. Gregory
• Reporter: Gary D. Gregory
• Created: 27/Oct/15 16:51
• Updated: 23/Dec/21 16:29
• Resolved: 02/Jun/16 20:58

Description

The Logger cache does not account for a logger's message factory.

If you call LogManager.getLogger(Class|Object|String, MessageFactory) and then call a getLogger() API again with the same Class|Object|String a different message factory, you get the Logger that was first created which means you will not get the proper formatted messages.

For example:

Logger loggerA1 = LogManager.getLogger("A", messageFactory1);
Logger loggerA2 = LogManager.getLogger("A", messageFactory2);

loggerA1 is the same as loggerA2.

This is a problem if two unrelated code bases (jars) both the same Logger names|objects|classes.

Issue Links

• is related to: LOG4J2-1407 Misleading WARN log events from Log4j about message factories and unexpected formatting
• is superceded by: LOG4J2-1404 log4j-slf4j-impl 2.6 is warning