Re: WAR class loader policy issue with Log4j2 migration

2022-03-02 Thread Ralph Goers
I am really not all that clear on what your setup is. A typical Tomcat setup would have a ClassLoader for Tomcat and a ClassLoader for each web application. These web applications each have multiple jars & packages and work fine. I am not clear what the “main package” is. When you say “single c

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