[
https://issues.apache.org/jira/browse/LOG4J2-3674?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Piotr Karwasz resolved LOG4J2-3674.
-----------------------------------
Resolution: Fixed
[~tilman] ,
Thank you for your report. This was also reported in:
[https://github.com/apache/logging-log4j2/issues/1865]
and fixed in version 2.21.0.
**Remark**: these days Github Issues is the recommended way to report issues.
> log4j2 with commons-logging no longer works since 2.21.0, worked with 2.20.0
> ----------------------------------------------------------------------------
>
> Key: LOG4J2-3674
> URL: https://issues.apache.org/jira/browse/LOG4J2-3674
> Project: Log4j 2
> Issue Type: Bug
> Components: JCL Bridge
> Affects Versions: 2.21.0
> Reporter: Tilman Hausherr
> Priority: Major
> Fix For: 2.21.1
>
> Attachments: Log4j2Reproducer.zip
>
>
> According to https://logging.apache.org/log4j/log4j-2.2/log4j-jcl/index.html
> the bridge should "just work". However since 2.21.0 log4j is no longer
> recognized, one needs to add the property file with
> {noformat}
> org.apache.commons.logging.LogFactory=org.apache.logging.log4j.jcl.LogFactoryImpl
> {noformat}
> this wasn't needed with 2.20.0. The attached project has the property file
> with a "_" ( _commons-logging.properties") one has to remove it to make the
> project work.
> What should happen:
> {noformat}
> 23.10.2023 11:03:49 INFO log4j2reproducer.Main:21 - yeah
> {noformat}
> What actually happens:
> {noformat}
> Okt 23, 2023 11:03:09 AM com.mycompany.log4j2reproducer.Main doStuff
> INFORMATION: yeah
> {noformat}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
