Versions Compared

Old Version 5

changes.mady.by.user Massimiliano Turri

Saved on

compared with

New Version 6

changes.mady.by.user Massimiliano Turri

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Create a file called log4j.properties in WEB-INF/classes with the following content, where you have replaced APPLICATION_OUTPUT_FILE with your choice of output file name (it would be nice to have in it the name of the application that produced the file):

Code Block
#
# Configures Log4j as the Tomcat system logger
#

#
# Configure the logger to output info level messages into a rolling log file.
#
log4j.rootLogger=INFO, R

#
# Default output file name
#
application.context=Commons

#
# Configuration for a rolling log file ("tomcat.log").
#
log4j.appender.R=org.apache.log4j.RollingFileAppender

#
# Edit the next line to point to your logs directory.
# The last part of the name is the log file name.
#
log4j.appender.R.File=${catalina.base}/logs/${application.context}APPLICATION_OUTPUT_FILE.log
log4j.appender.R.layout=org.apache.log4j.PatternLayout
log4j.appender.R.MaxFileSize=5036KB
log4j.appender.R.MaxBackupIndex=4

#
# Print the date in ISO 8601 format
#
log4j.appender.R.layout.ConversionPattern=%d %-5p - %m%n

If you now redeploy your application all the output from your application should be logged in the file you chose.

Monitoring the log file

Use probe to monitor the log file produced by your application going to:

http://_serverName_.slac.stanford.edu:8080/probe/logs/

where serverName is the tomcat server on which the application has been deployed.