Good idea, I'll try that and see what I get. Thanks. On Tue, Aug 26, 2008 at 6:07 PM, Ian Roberts <[EMAIL PROTECTED]>wrote:
> Daniel Kulp wrote: > > Not really sure. I guess my suggestion would be to pull the log4j jar > (if > > possible) and seeing if that would allow more logging statements to come > up. > > One of my "issues" with log4j is that if it's not configured, it > sometimes > > decides not to log anything. Alternatively, put log4j into the tomcat > paths > > and provide a log4j config file to tomcats startup params to make sure > it's > > picked up. > > Or alternatively just create a simple log4j.properties in your > WEB-INF/classes, something like: > > log4j.rootLogger=DEBUG, stdout > log4j.appender.stdout=org.apache.log4j.ConsoleAppender > log4j.appender.stdout.layout=org.apache.log4j.PatternLayout > log4j.appender.stdout.layout.ConversionPattern=%5p [%t] (%F:%L) - %m%n > > This should dump all the debug logs into catalina.out. Or if that's too > noisy then replace the rootLogger line with these two lines, which will > make Spring log at debug level and everything else at info level: > > log4j.rootLogger=INFO, stdout > log4j.logger.org.springframework=DEBUG > > Ian > > -- > Ian Roberts | Department of Computer Science > [EMAIL PROTECTED] | University of Sheffield, UK >
