jGuru: Is this normal to see? Is there a way to turn this off??: "The digester class that tomcat uses to process its config files output an unholy amount of debug information through log4j. I am guessing that you enabled log4j debugging for your webapps and are now seeing the internal logs for Tomcat. You have two options:
First, you can move log4j into your webapp. Since this will be loaded as part of its own classloader, it should not get the Tomcat internal stuff. If you want a global log4j config for all webapps, you can probably put the jar in shared/lib.
Second, you can disable debug logging for specific categories(or globally) that are causing you grief. To disable debug logging globablly, in your log4j config file (specified with -Dlof4j.configuration=file:log4j.properties or the log4j.properties file on the classpath), add the line
log4j.threshold=info
To disable it for a specific category:
log4j.logger.org.apache.commons.digester.Digester=info
If you are using an old version of log4j, the property names change a bit. I think that log4j.logger is changed to log4j.category and log4j.threshold is changed to log4j.priority, but I can't quite remember.
Hope this helps."
Tuesday, April 12, 2005
Subscribe to:
Post Comments (Atom)
Popular Posts
- Creating an as400 Query
- ibm as400 manuals v5r4
- Library list for Web server
- UDATE and *DATE in AS400 RPG
- OS/400 PASE Shells and Utilities
- AS400 Job Scheduler
- IBM WebSphere Developer Technical Journal: Maintain continuous availability while updating WebSphere Application Server enterprise applications
- Recover or reset QSECOFR passwords
- Encrypt Data on as400 (QC3ENCDT, Qc3EncryptData)
- Getting Around the Java Compiler's 64K Limitation
No comments:
Post a Comment