-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Sat, 24 Dec 2005, Sylvain Wallez wrote:
Date: Sat, 24 Dec 2005 10:01:04 +0100
From: Sylvain Wallez <[EMAIL PROTECTED]>
Reply-To: [email protected]
To: [email protected]
Subject: Re: Behaviour of LogKit
Giacomo Pati wrote:
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
It seems to me that the LogKit (precisely the rootLogger of it) gets it
Priority setup much later in the initialization phase in 2.2 as it was in
2.1. Nobody else got bored about the flood of debugging messages at
startup?
Oh yes! I tried to fix it by ensuring Cocoon uses the default hierarchy,
which is also used by commons-logging, but that didn't removed all the flood.
The cause is at line 413 in [1], #unsetPriority(...) method, where the
default Priority is set to DEBUG.
Do you mean we should set the default priority to a higher level? Makes
sense, but AFAICS it's has been DEBUG for ages, and I don't understand why
there's no flood in 2.1...
Maybe the setup process has changed before the LogKitManager is able to
setup the correct Priority to the rootLogger? Did we changed the use of
commons-logging from 2.1 to 2.2 ? lots of questions I cannot answer as I
probably have missed that transition.
I've tested with my own Logger class in WEB-INF/classes with a higher
Priority set and it prevents the flood.
- --
Giacomo Pati
Otego AG, Switzerland - http://www.otego.com
Orixo, the XML business alliance - http://www.orixo.com
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (GNU/Linux)
iD8DBQFDrT+5LNdJvZjjVZARAgatAKCw3Q2IIo/tLAe0ZmSJ/VvMqy+HHQCbB7c9
AtoRcFOOhM/cr1YM5yKqwYA=
=zJrz
-----END PGP SIGNATURE-----
