WAR class loader policy issue with Log4j2 migration

2022-03-02 Thread Markos, Alazar A
When working with applications which have multiple jars/packages, logging stops after upgrading to Log4j 2.17.1. Only the main package where the app is initialized is logging. It seems to be a class loader issue. To resolve this, we had to go into the deployed jar in websphere and change WAR cl

WAR class loader policy affecting Log4j2 migration

2022-03-02 Thread Markos, Alazar A
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