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 configura
What happens if you update to 2.17.2?
Gary
On Wed, Mar 2, 2022, 14:26 Markos, Alazar A
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,
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 loa
