I don’t really know what “the solution listed above” is. I don’t see anything in my email.
I thought I responded to this that your app has multiple LoggerContexts. This is by design. It seems only one of them has a log4j2.xml configured so the others are most likely using the default configuration and logging errors to stdout. If you only want a single LoggerContext then you need to use a different ContextSelector. Ralph > On Mar 2, 2022, at 10:08 AM, Markos, Alazar A > <[email protected]> wrote: > > When working with an application which has multiple jars/packages, logging > stops after upgrading to Log4j 2.17.1. Only the main package where the app is > initialized is logging. To resolve this, we had to go into the deployed jar > in websphere and change WAR class loader policy to single class loader for > application. After making this change, all the logs can be seen for all the > jars. Is there a workaround for this issue besides the solution listed above? > > Alazar Markos > Associate IT Developer > 678 614 0234 > [email protected] <mailto:[email protected]>
