-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Beeky,
On 3/27/2009 11:13 AM, beeky wrote: > -------log4j.config in <catalina_home>/common/classes---------- > log4j.rootLogger=ERROR, stdout, TOMCAT This should only allow ERROR or higher messages to be logged, unless another logger has explicitly set a lower log level to be logged (and that logger is being used). That does not appear to be the case, here. > ----------- log4j.config in the applications WEB-INF dir -------------------- > > log4j.rootCategory=debug, OBIS This is likely to be the source of the problem: you have defined the root logger (rootCategory is deprecated in favor of rootLogger) to have a log level of DEBUG. This will affect any log messages emitted by your application. Note that certain loggers have been silenced wrt DEBUG messages: > # Suppress the tomcat logging whilst DEBUG is switched on > log4j.logger.org.apache.catalina.core=ERROR > log4j.logger.org.apache.catalina.session=ERROR > log4j.logger.org.apache.jasper.compiler=ERROR ... and others have been allowed to spew everything: > # Spring logging > #log4j.logger.org.springframework=TRACE SmapUtil is in the org.apache.jasper.compiler package, so you need to add configuration for that. It looks like you already have one: > log4j.logger.org.apache.jasper.compiler=ERROR If your config file really is called log4j.config, then it might not be properly read: the file is typically called log4j.properties. Are you manually loading thr configuration file, or are you allowing log4j to automagically load it for you? - -chris -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAknM9yAACgkQ9CaO5/Lv0PCNbwCgqXOareEOR6EH35+MoBzDaV2t UnMAoLagZAH/rvolh4NKL5xGI7S0DDVc =GBmr -----END PGP SIGNATURE----- --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
