kostya-sh opened a new issue, #3461: URL: https://github.com/apache/logging-log4j2/issues/3461
## Description It appears that AbstractLogger.checkMessageFactory expects the default message factory to be ParameterizedMessageFactory (https://github.com/apache/logging-log4j2/blob/c59fdd4a0e1478da3a0260ed07e07488f199e221/log4j-api/src/main/java/org/apache/logging/log4j/spi/AbstractLogger.java#L187). However if thread locals are enabled the default message factory is ReusableMessageFactory (https://github.com/apache/logging-log4j2/blob/c79ae325f6a21af45526c202f121bfced188613e/log4j-core/src/main/java/org/apache/logging/log4j/core/Logger.java#L114) ## Configuration **Version:** 2.24.0 **Operating system:** [OS and version] **JDK:** 17 ## Logs ``` 2025-02-12T10:31:17.559492800Z main WARN The Logger Log4JMessageFactoryWarning was created with the message factory org.apache.logging.log4j.message.ReusableMessageFactory@32ee6fee and is now requested with a null message factory (defaults to org.apache.logging.log4j.message.ParameterizedMessageFactory), which may create log events with unexpected formatting. ``` ## Reproduction Log4j configuration should have status="info" enabled. ``` import org.apache.logging.log4j.LogManager; public class Log4JMessageFactoryWarning { public static void main(String[] args) { LogManager.getLogger(Log4JMessageFactoryWarning.class); LogManager.getLogger(Log4JMessageFactoryWarning.class); } } ``` -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: notifications-unsubscr...@logging.apache.org.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
