RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

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.

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