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 class loader policy to single class loader for application. After that, we could see all the logs from all the jars. Is there a workaround to this issue? It seems to be consistent across multiple applications. Some feedback would really help, thanks!
Alazar Markos Delta Air Lines Associate IT Developer 678-614-0234 [email protected]<mailto:[email protected]> [cid:47a3ad1b-8b1a-4d17-924d-cd1991115a9e]
