Hi All:

I have a bug in a web app where I use log4j-web:
- Tomcat 9 correctly starts Log4j 2 FIRST, BEFORE the web-app, which is correct.
- The App runs and uses Log4j 2
- When I stop or undeploy the web app, Tomcat complains about a Log4j
thread still hanging around because:
- Tomcat stops Log4j FIRST (which is wrong for this stack).
- Tomcat stops the web-app which cause some logging
- Log4j re-initializes itself

So... Can we fix this in our web fragment? Can we say "start first and
stop last"?

Can I say that at all in server.xml? Does Servlet 5.0 (Tomcat 10) help?

TY!
Gary

---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-user-unsubscr...@logging.apache.org
For additional commands, e-mail: log4j-user-h...@logging.apache.org

Reply via email to