Initializing Log4j1 bridge with properties object blocks Log4j2 logging since 2.17.2 about logging-log4j2

[ppkarwasz]

PropertyConfigurator#configure() was a no-op before version 2.17.2 (cf. source code).

The call must provide a broken configuration (you can debug it by running -Dlog4j2.debug=true), hence the logs vanish.

[mbain-cincom]

@ppkarwasz

Thank you for the reply, it filled in the piece I was missing. It wasn't a broken configuration, rather an incorrect mindset on my part. Previously this application was using Log4j2 and Log4j1 for independent purposes. In 2.17.1 we were able to get the proper result based on the configure() option not doing anything and having a logger that matched in our log4j2.xml. As soon as it was actually performing an initialization it is now overwriting our log4j2 configuration with our legacy Log4j1 configuration, and our Log4j2 usage in essence no longer has loggers to work with. We will have to look into potential solutions either through context or creating a custom configuration factory, etc.

[ppkarwasz]

There is an open JIRA issue (LOG4J2-3467) to provide users a way to disable the improvement in log4j-1.2-api introduced in version 2.17.2. We should probably consider it solving it.