[ https://issues.apache.org/jira/browse/LOG4J2-3467?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17518256#comment-17518256 ]
Alexander Veit edited comment on LOG4J2-3467 at 4/6/22 3:57 PM: ---------------------------------------------------------------- Unfortunately I cannot provide a test application to reproduce the problem with the actual dependencies (third-party library, closed-source). However, the smallest program to reproduce the issue is probably the following (derived from bytecode): {code:java} import java.util.Properties; import org.apache.log4j.PropertyConfigurator; import org.slf4j.Logger; import org.slf4j.LoggerFactory; private static final Logger logger = LoggerFactory.getLogger(Test.class); logger.error("ERROR1"); PropertyConfigurator.configure(new Properties()); logger.error("ERROR2"); {code} Hereby {{logger}} is a SLF4J logger with a Log4J backend and configuration. Only ERROR1 is being logged. was (Author: veita): Unfortunately I cannot provide a test application to reproduce the problem with the actual dependencies (third-party library, closed-source). However, the smallest program to reproduce the issue is probably the following: {code:java} import java.util.Properties; import org.apache.log4j.PropertyConfigurator; import org.slf4j.Logger; import org.slf4j.LoggerFactory; private static final Logger logger = LoggerFactory.getLogger(Test.class); logger.error("ERROR1"); PropertyConfigurator.configure(new Properties()); logger.error("ERROR2"); {code} Hereby {{logger}} is a SLF4J logger with a Log4J backend and configuration. Only ERROR1 is being logged. > Update from Log4J 2.17.1 to 2.17.2 breaks application > ----------------------------------------------------- > > Key: LOG4J2-3467 > URL: https://issues.apache.org/jira/browse/LOG4J2-3467 > Project: Log4j 2 > Issue Type: Bug > Components: Core > Affects Versions: 2.17.2 > Reporter: Alexander Veit > Priority: Major > > We have an application that uses a third-party library which seems to > reconfigure Log4J according to its needs. This worked for quite some years > with various Log4J versions. > After upgrading from Log4J 2.17.1 to 2.17.2 a call to the library immediately > stops logging completely in the sense that no further logging is performed > until restarting the JVM. > We've tried to identify the change that leads to the problem. Our best guess > is PropertyConfigurator, line 164 in > https://github.com/apache/logging-log4j2/commit/73a2cd1cd0e94c7f4f36e4ac9dc72380d30750ef#diff-607596a6cadd10faf2dbeefc4e03092264b8e0dbe23fb89ffa6505d644602c9dR164 > Note that according to semantic versioning such breaking changes should not > occur when only the patch version is incremented. ;-) -- This message was sent by Atlassian Jira (v8.20.1#820001)