I've stumbled across a problem with some static loggers. The general
pattern is:

- TCCL is web application class loader
- static logger is created
- static logger is associated with web application class loader
- web application is undeployed
- appenders are removed from logger
- further logger output is lost

In most cases we avoid this issue by using a non-static logger. I've
found a few places where we need to switch from static to non-static
loggers. That in turn is triggering some refactoring (as static methods
can't access a non-static logger).

I should have something ready to commit later today.


To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org

Reply via email to