All,
We'd like to replace Tomcat's built-in logging with Log4J2, and are able
to do so based on Tomcat's docs for using Log4J 1.x, and deploying the
log4j-1.2-api-2.0-beta4.jar shim.
However, we're running into an issue with external configuration...
Our webapps are always deployed with external logging configuration
files. Historically, we've used
-Dlog4j.configuration=/path/to/log4j.properties (now
-Dlog4j.configurationFile=/path/to/log4j2.xml) to point the app to the
correct file.
Unfortunately, if we pass the app-specific config file to the Tomcat
JVM, the Tomcat-level Log4J2 instance *also* tries to that config file.
Is there a reasonable way to support externalized configuration files
both for the Tomcat-level Log4J2 instance, *and* app-specific external
configuration files as well?
Many thanks,
--Scott
---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org
For additional commands, e-mail: log4j-dev-h...@logging.apache.org
