Try starting tomcat with the system property log4j.debug set for example : export TOMCAT_OPTS="-Dlog4j.debug"
IIRC, log4j will output info about which config file it's using to standard output. see also http://logging.apache.org/log4j/1.2/manual.html Maarten On Wed, Mar 31, 2010 at 9:22 PM, Egan, David <[email protected]>wrote: > Following the instructions from here: > http://tomcat.apache.org/tomcat-6.0-doc/logging.html#log4j. > specifically the end 2nd last paragraph about config web application > logging. > > > My application (SOAP service) runs successfully AND logs when I run locally > on my Window Tomcat 6 instance (both to console and log file specified in > log4j.properties). > > Migrate the SAME war file to Solaris test environment, with same > WEB-INF/classes/log4j.properties file > WEB-INF/lib/log4j-1.2.14.jar > > When migrated to our Solaris environment running same version of Tomcat > (6.0.24) absolutely no logging occurs. Nothing showing in console log nor > in log file specified. It's as if it's going completely to /dev/null.... > > There is an older jar for log4j in the classpath for Tomcat for Axis. > However my understanding is my web application will use the properties and > jar file in the war file path. And I'm not using Axis. > > Absolutely baffed - works perfectly fine locally but not at all on Solaris > test server. Getting zero error messages so it's as if it's getting blocked > somehow. Yet the application runs and logging should be happening. > > I'd include the log4j.properties but it's not relevent - the same file > works fine locally but no errors or results on Solaris. > > Thoughts/ideas where to look? > > -- > David Egan > >
