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? I verified that there is indeed no such log4j.properties file, and the logging.properties file is in the correct location. The project I'm (attempting) to work on is a well known open source enterprise LMS system. It is a very large system, comprised of 100+ sub projects within the project itself. Building and dependencies are handled by Maven. Not sure if that info helps with anything. Thanks again, Brian J. -----Original Message----- From: Mark Thomas [mailto:ma...@apache.org] Sent: Friday, October 21, 2011 3:31 PM To: Tomcat Users List Subject: Re: Tomcat produces empty/missing log files On 21/10/2011 20:27, Brian Jones wrote: > My mistake. The distro doesn't include the .jar by default. The project I > deploy to Tomcat automatically sticks the log4j.jar file there. > > Sorry for the confusion; I overlooked this step. That begs the question "What else is it doing?" since it appears to be breaking the Tomcat logging configuration. Mark --------------------------------------------------------------------- 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
