Details
-
Feature Request
-
Resolution: Duplicate
-
Major
-
None
-
None
-
Documentation (Ref Guide, User Guide, etc.)
-
0
-
0%
Description
A deployment local common logging properties pointing to a log4j factory with a deployment log4j.properties will not pickup the log4j configuration because we do not allow reloading of the commons-logging classes. This is due to the way tomcat uses commons-logging causing problems with deployments that include commons-logging. The side-effect of this is that the runtime resolution of the log4j factory does not trigger reloading of the deployment local log4j singleton and properties.
One way to address this is by using a log4j factory that uses dynamic proxies to locate the actual log4j classes at runtime based on the thread context class loader so that the log4j version is not bound to the shared commons-logging classes. Another would be to use a factory that used a deployment local logger repository.