2012/2/15 Pid <p...@pidster.com>: > On 14/02/2012 21:49, Marcel Stör wrote: >> It seems nowadays you need a PHD just to understand Tomcat >> logging...sigh. In one of my Eclipse/WTP projects Tomcat logs each >> request (before and after): >> >> ... >> 13.02.2012 20:50:47 org.apache.catalina.core.ApplicationContext log >> INFO: After request >> [uri=/demo-webmvc-web/scripts/libs/jquery/jquery-1.6.4.min.js?null] >> 13.02.2012 20:50:47 org.apache.catalina.core.ApplicationContext log >> INFO: Before request [uri=/demo-webmvc-web/images/logo.gif?null] >> 13.02.2012 20:50:47 org.apache.catalina.core.ApplicationContext log >> INFO: After request [uri=/demo-webmvc-web/images/logo.gif?null] >> ... >> >> How do I get rid of this? > > Tomcat doesn't log an INFO level output for that - have you by any > chance got a Servlet Filter in your application? >
One more. If Tomcat logging is indeed used, then any logging.properties file in the classpath will change logging configuration for the classloader that it is accessible from. Here is such problem reported caused by jollyday library that contained a logging.properties file: https://issues.apache.org/bugzilla/show_bug.cgi?id=52011 This feature is usually used by web applications when they provide their own WEB-INF/classes/logging.properties file. Best regards, Konstantin Kolinko --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
