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
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Dan,
On 4/6/2009 5:42 PM, Dan Armbrust wrote:
System.setProperty(log4j.defaultInitOverride, true);
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
On Thu, Apr 2, 2009 at 9:55 PM, Caldarale, Charles R
chuck.caldar...@unisys.com wrote:
From: Dan Armbrust [mailto:daniel.armbrust.l...@gmail.com]
Subject: And even further into the black magic of logging configuration
within tomcat...
So, why didn't log4j try to find the log4j.properties
So, after my long thread to figure out the missing stack traces from a
bad listener configuration, I _thought_ I knew what I needed to
correct.
It seemed that Tomcat was trying to use log4j shipped with my webapp,
before my webapp had configured log4j.
Supplying a log4.properties file in the
From: Dan Armbrust [mailto:daniel.armbrust.l...@gmail.com]
Subject: And even further into the black magic of logging configuration
within tomcat...
So, why didn't log4j try to find the log4j.properties
file for the second webapp?
Verify that you have separate log4j.properties files
