Bug 2136405

Summary: Log4j - Appender not available - rebase to log4j-2.17.2 [rhel-9]
Product: Red Hat Enterprise Linux 9 Reporter: Marián Konček <mkoncek>
Component: log4jAssignee: Marián Konček <mkoncek>
Status: CLOSED ERRATA QA Contact: Martin Kyral <mkyral>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: unspecifiedCC: mkyral
Target Milestone: rcKeywords: Triaged
Target Release: ---Flags: pm-rhel: mirror+
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: log4j-2.17.2-1.el9 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2023-05-09 07:32:28 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Marián Konček 2022-10-20 08:38:14 UTC
This bug was initially created as a copy of Bug #2123349

I am copying this bug because: 
Different product


User explanation about the existing RollingFileAppender class in log4j-2.17.1,
and need for log4j-2.17.2 is that log4j-2.17.1-4 also has RollingFileAppender
in log4j-core module (org.apache.logging.log4j.core.appender) but package
hierarchy is not same as org.apache.log4j.RollingFileAppender.

We require the RollingFileAppender from Bridge API i.e.,
"log4j-1.2-api-2.17.1.jar" module with package structure
org.apache.log4j.RollingFileAppender, which will take lesser efforts and time
and thus will help in easier migration from Log4j 1.x to Log4j 2.x.

The class org.apache.log4j.RollingFileAppender is available in latest
"log4j-1.2-api-2.17.2.jar" which will help to resolve the issue we are facing.

Comment 9 errata-xmlrpc 2023-05-09 07:32:28 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (log4j bug fix and enhancement update), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2023:2197