Alexander Veit created LOG4J2-3467:
--------------------------------------
Summary: 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
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)
