We have Log4j packaged within the WAR for each of the deployed applications.
Under run-time configuration I mean editing the standard log4j.xml which is
re-read by Tomcat. (I.e. we do not want to reimplement any log level
configuration in servlet configuraton, what we want is to pass the locati
I am pretty sure I tried option 3 and Log4j initialization did ignore my
log4jConfigLocation setting in conf/.../myapp.xml.
What I tried to see in the debug log is the list of context parameters picked
up at start time. Despite log level was set to FINEST nothing show up in any of
the Tomcat lo
Thanks, I am afraid I read a similar solution earlier which I did not favour
for multiple reasons:
- it is a run-time configuration question (handled by DevOps, Ops) to have
various logging levels for various deployed applications on the same Tomcat
- we would like to have full control of loggin
Hello
We have a setup which compiles WAR applications once and deploys them in
various environments. Each environment has its own per application Log4j
configuration (WARN for production, DEBUG for development etc.) which should
survive application redeployment.
So far the solution is:
webapp
