Alright, for the archive, this seems to be working nicely...
/usr/local/applications/tomcat4.1.24/common/classes/log4j.properties
contains:
# log4j.properties
#
# This file will shut off these messages in catalina.out...
#
# 5189887 [Thread-14] INFO common.ChannelSocket - connection timeout
reached
#
#
########################################################
## LOGGING MESSAGES..... ##
########################################################
log4j.category.org.apache.jk.common.ChannelSocket=WARN, filer
log4j.additivity.org.apache.jk.common.ChannelSocket=false
log4j.appender.filer=org.apache.log4j.RollingFileAppender
log4j.appender.filer.layout=org.apache.log4j.PatternLayout
log4j.appender.filer.layout.ConversionPattern=%-5p %c - [%m]
%d{ISO8601}%n
log4j.appender.filer.File=/usr/local/applications/tomcat4.1.24/logs/cata
lina.debug
log4j.appender.filer.MaxFileSize=100KB
log4j.appender.filer.MaxBackupIndex=4
note you need to create the file:
/usr/local/applications/tomcat4.1.24/logs/catalina.debug
So far there seem to be no side-effects. All 'regular' system.out
messages make it to catalina.out. All other apps using log4j seem happy
as well. For the most part, the catalina.debug file ought to remain
empty. Unless of course, something actually happens in the
org.apache.jk.common.ChannelSocket class that is logged at WARN or
above.
> -----Original Message-----
> From: Shapira, Yoav [mailto:[EMAIL PROTECTED]
> Sent: Wednesday, October 15, 2003 9:24 AM
> To: Tomcat Users List
> Subject: RE: How to roll over catalina.out?
>
>
>
> Howdy,
>
> >there is mention of configuring logging.properties in JRE
> 1.4.x's lib
> >directory. Which would be for java.util.logging, not
> commons-logging.
> >So configuring commons-logging is the preferred way?
> >
> >Where would I place the commons-logging config file? In
> /common/classes
>
> Yes, commons-logging is the preferred way.
>
> You would place the commons-logging configuration in the same
> repository as commons-logging-api.jar or commons-logging.jar.
> (In the /classes, not /lib, part of the repository). So if
> you have commons-logging.jar in common/lib, you would place
> the configuration file on common/classes.
>
> Placing it in the same repository is not strictly required,
> but is probably the least confusing of the alternative approaches.
>
> Yoav Shapira
>
>
>
> This e-mail, including any attachments, is a confidential
> business communication, and may contain information that is
> confidential, proprietary and/or privileged. This e-mail is
> intended only for the individual(s) to whom it is addressed,
> and may not be saved, copied, printed, disclosed or used by
> anyone else. If you are not the(an) intended recipient,
> please immediately delete this e-mail from your computer
> system and notify the sender. Thank you.
>
>
> ---------------------------------------------------------------------
> 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]
