Tomcat5Logging

This is version 7. It is not the current version, and thus it cannot be edited.
[Back to current version]   [Restore this version]

Create a log4j.properties file in $CATALINA_HOME/common/classes

log4j.rootLogger=ERROR, R
log4j.appender.R=org.apache.log4j.DailyRollingFileAppender
log4j.appender.R.File=${catalina.home}/logs/tomcat.log
log4j.appender.R.DatePattern='.'yyyy-MM-dd
log4j.appender.R.layout=org.apache.log4j.PatternLayout
log4j.appender.R.layout.ConversionPattern={%p} %c{2} %x %m%n

You also need to copy commons-logging.jar and log4j-1.2.9.jar to $CATALINA_HOME/common/lib. Note, some references say copy these files to $CATALINA_HOME/server/lib, but for me, copying to common/lib worked fine.

Then, in your application log4j.properties file ($APPFUSE_HOME/web/WEB-INF/classes), add this:

# Suppress the tomcat logging whilst DEBUG is switched on
log4j.logger.org.apache.catalina.core=ERROR
log4j.logger.org.apache.catalina.session=ERROR
log4j.logger.org.apache.jasper.compiler=ERROR

Because if, whilst developing, you set your root logger to DEBUG, then it seems to set the Tomcat logging to DEBUG as well, and you will probably witness thousands of lines of compilation trace from the Jasper compiler!

It is of course, better practice, to keep your application log4j.properties ROOT log level set to WARN or ERROR, and just turn on debugging for your own application classes! (ie. org.appfuse=DEBUG )