Konstantine and Mark, Thanks to both of you for your revelations; without you two I would truly be lost.
That defiantly makes sense. Are there any known workarounds for using java.util.logging instead of log4j even if the log4j.jar file is present? Thanks again for allowing me to pick your brain. Brian J -----Original Message----- From: Konstantin Kolinko [mailto:knst.koli...@gmail.com] Sent: Friday, October 21, 2011 3:40 PM To: Tomcat Users List Subject: Re: Tomcat produces empty/missing log files 2011/10/21 Brian Jones <bjone...@uwo.ca>: > Yes, it appears that the project I'm deploying is relying on log4j for > logging; so when I remove the log4j.jar file, it obviously complains that it > can't find it. > > However, what I don't understand is why Tomcat refuses to log to the log > files if there is a log4j.jar file present in the common/lib folder. > Shouldn't it be looking for the log4j.properties file to determine if it > uses log4j or commons? That "commons" is a wrapper that autoselects either java.util.logging or log4j See http://commons.apache.org/logging/ logging.properties is configuration file for java.util.logging. Dropping in log4j*.jar is enough to confuse the wrapper so that effectively logging.properties is not used at all. --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
