Here is my log4j.properties file:
log4j.rootLogger=INFO, R
log4j.appender.R=org.apache.log4j.RollingFileAppender
log4j.appender.R.File=${catalina.home}/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=INFO, R
It was my understanding the under the rules of Log4j inheritance, all
loggers would inherit from the first non-null ancestor starting with the
parent and working toward the root. I believe that this means that I
should only be getting INFO level messages, no?
Brad
Rob Gregory wrote:
Please post your log4j.properties file - it sounds like your root logger is
too general.
Rob
-----Original Message-----
From: Brad O'Hearne [mailto:[EMAIL PROTECTED]
Sent: 24 February 2006 19:35
To: Tomcat Users List
Subject: tomcat catalina.out getting bombed with debug messages on
maven-proxy deploy
I have a vanilla installation of Tomcat 5.5 (with logging added, and
log4j.properties rootLogger set to level INFO), which starts up cleanly,
and writes maybe 15 lines to catalina.out -- no more. I then deploy the
maven-proxy-webapp.war, and catalina.out gets immediately bombed with
DEBUG level messages. It appears that most of the messages are coming
from the commons.digester and digester packages. Does this problem lie
in Tomcat, or in the web app? How do I filter the LOG level for this
information?
Thanks!
Brad
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
