Unless I'm missing something somewhere else, catalina.sh specifies
that logging.properties is the java.util.logging configuration file
used. I suppose changing the jre properties file is an option, though
if that works it leaves a big questions as to why this is the case.
Is anyone else hav
Brad O'Hearne wrote:
This is a real incredible nuisance. It appears that Tomcat is using
java.util.logging, so I altered all the log levels in
conf/logging.properties to WARNING, and I'm still getting DEBUG messages
Since you're using java.util.logging, have you tried the
logging.properties
ob 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 de
omcat 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
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-
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
