Index: logging.xml
===================================================================
RCS file: /home/cvspublic/jakarta-tomcat-catalina/webapps/docs/logging.xml,v
retrieving revision 1.1
diff -u -r1.1 logging.xml
--- logging.xml 7 Oct 2004 18:16:05 -0000 1.1
+++ logging.xml 15 Nov 2004 15:41:33 -0000
@@ -4,32 +4,140 @@
]>
+ Tomcat 5.5 has done away with with localhost_log which you may be familiar with
+ as the runtime exception/stack trace log. These types of error are usually thrown
+ by uncaught exceptions, but are still valuable to the developer. They can now be
+ found in the stdout log.
+
+ If you need to setup cross-context detailed logging from within Tomcat's code, then you can use a simple
+ log4j configuration. Note that this logging van be very verbose depending on the log level you chose to use.
+ Note also that a log4j logging configuration is not going to produce stack trace type logging, that is output to
+ stdout as discussed.
+ Follow the following steps to setup a file named tomcat.log that has internal Tomcat logging output to it.
+ This log4j configuration sets up a file called tomcat.log in your Tomcat logs folder with a maximum file size of 10MB and
+ up to 10 backups. DEBUG level is specified which will result in the most verbose output from Tomcat. The above generated
+ about 5MB of logging with bundled web applications and Struts web applications.
+
+ You can of course choose to be more picky about which packages to include in the logging. For example try substituting the
+ last line of the above configuration with one of these:
+
+
+
+
+ log4j.rootLogger=debug, R
+ log4j.appender.R=org.apache.log4j.RollingFileAppender
+ log4j.appender.R.File=d:/jakarta-tomcat-5.5.4/logs/tomcat.log
+ log4j.appender.R.MaxFileSize=10MB
+ log4j.appender.R.MaxBackupIndex=10
+ log4j.appender.R.layout=org.apache.log4j.PatternLayout
+ log4j.appender.R.layout.ConversionPattern=%p %t %c - %m%n
+ log4j.logger.org.apache.catalina=DEBUG, R
+
+
+
+
The usefulness of what you will find from the log4j logging is debatable and will depend on your needs. Your + web applications should certainly use their own log4j configuration. This is valid with the above. + You would place a similar log4j.properties file in your web application's WEB-INF/classes folder, and log4j1.2.8.jar into + WEB-INF/lib. Then specify your package level logging. This is a basic setup of log4j and you should consult the log4j + documentation for more options, but hopefully this section will get you up to a basic speed. +
+ - +