Apologies for replying late to this...

I've learned that in production, I set my log level to INFO or higher:

# Set root category priority to INFO to stop all the *trash*
log4j.rootCategory=INFO, LOGFILE

But setting my default to INFO, I need to be careful in my LOGFILE
definition so I can trap anything lower.  So I set up LOGFILE as:

# LOGFILE is set to be a File appender using a PatternLayout.
log4j.appender.LOGFILE=org.apache.log4j.RollingFileAppender
log4j.appender.LOGFILE.File=${catalina.home}/logs/logfile.txt
log4j.appender.LOGFILE.Append=true
log4j.appender.LOGFILE.MaxFileSize=1MB
log4j.appender.LOGFILE.MaxBackupIndex=10
log4j.appender.LOGFILE.Threshold=DEBUG
log4j.appender.LOGFILE.layout=org.apache.log4j.PatternLayout
log4j.appender.LOGFILE.layout.ConversionPattern=%-4r [%t] %-5p %c %x - %m%n

No, you need to be aware that I have 10 backup files defined above.
Because of this, your catalina.policy file needs to give read and write
permissions to all 10 files or you will get security errors from the
JVM.

So, how do I get errors from my specific modules?  If I have modules
that I need more info from, I set the specific modules level in my
properties file.  For example:

# Specific app debugging stuff...
log4j.logger.com.sequoia.tag1_library.ClientCode2Tag=DEBUG

I use this a LOT in my debugging and QA environments to isolate 
errors to the offending module(s) only.


Another poster mentioned that this setup requires posting my WAR 
to the server in order to change the level(s) of my modules.  But
in my environment, posting the app. to the production server isn't 
something we do all that often.  While debugging in QA / Development
IS something I do every day.


Hope this helps!

Bob

On Fri, 2005-10-14 at 14:59 +0200, Christoph P. Kukulies wrote:
> I learnt that tomcat 5.5 uses a different logging facility and doesn't seem
> to log by default.
> 
> So I installed log4j and commons-logging as of the instructions under
> http://tomcat.apache.org/tomcat-5.5-doc/logging.html
> 
> but with the proposed loglevels it is hard to fish out any relevant 
> information
> of simple things like why a request could not be fulfilled.
> 
> Instead tomcat logs loads of information even while idling.
> 
> What would be a useful setting of the loglevel as used for example
> in the default settings of apache?
> 
> 
> --
> Chris Christoph P. U. Kukulies kuku_at_kukulies.org
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
> 
-- 
Bob Bateman
The Computer Guy
Sequoia Group LLC
248 414-7288
248 414-7541 (fax)


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to