[
https://issues.apache.org/jira/browse/LOG4J2-3467?focusedWorklogId=927898&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-927898
]
ASF GitHub Bot logged work on LOG4J2-3467:
------------------------------------------
Author: ASF GitHub Bot
Created on: 30/Jul/24 08:40
Start Date: 30/Jul/24 08:40
Worklog Time Spent: 10m
Work Description: ppkarwasz opened a new issue, #2778:
URL: https://github.com/apache/logging-log4j2/issues/2778
This issue is moved from the
[LOG4J2-3467](https://issues.apache.org/jira/browse/LOG4J2-3467) JIRA issue.
The `log4j-1.2-api` artifact is a bridge, whose main purpose is to forward
Log4j 1 "API" calls to Log4j 2 API.
Version 2.17.2 of the artifact introduced support for configuring Log4j Core
using the Log4j 1 `PropertyConfigurator` and `DOMConfigurator` classes.
This feature should be disable by default and depend on the opt-in
`log4j1.compatibility` property, because:
* many third-party **libraries** (not related to logging) take upon
themselves the reconfiguration of Log4j 1. This steals the control of logging
configuration from application developers (see [How to disable log4j
programmatic reconfiguration from a 3rd party
jar](https://stackoverflow.com/questions/78801614/how-to-disable-log4j-programmatic-reconfiguration-from-a-3rd-party-jar)
for example).
* if some **applications** actually use those classes, they can always set
`log4j1.compatibility` to `true`. This configuration property is also used to
enable the scanning of the classpath for `log4j.properties` and `log4j.xml`
files.
Issue Time Tracking
-------------------
Worklog Id: (was: 927898)
Remaining Estimate: 0h
Time Spent: 10m
> 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
> Time Spent: 10m
> Remaining Estimate: 0h
>
> 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.10#820010)
