> If you deploy more than one
> webapp, log4j doesn't attempt to self-configure in the second or any
> subsequent webapps.
>
Just to close out this thread - no big surprise here - I found the bug
in a library that I was deploying in one of my webapps that caused
this behaviour.
Some code was executing this:
System.setProperty("log4j.defaultInitOverride", "true");
in a static init block.
Depending on the order that the static init blocks would be run (this
first, or log4j's first) would change whether log4j would try to
configure itself, since log4j pays attention to that System variable.
And also, since this is a global JVM variable, one webapp setting this
property would affect the behaviour of other webapps - but again, it
would be order dependant.
Dan
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org
