st to be declared in web.xml
Perhaps we're both dreaming :)
Cheers, Allistair.
-Original Message-
From: Rick [mailto:[EMAIL PROTECTED]
Sent: 14 November 2005 16:09
To: 'Tomcat Users List'
Subject: RE: Log4j issues upgrading from 5.5.9 to 5.5.12
Allistair,
Well, great . T
onday, November 14, 2005 7:50 AM
Posted To: Tomcat Dev
Conversation: Log4j issues upgrading from 5.5.9 to 5.5.12
Subject: RE: Log4j issues upgrading from 5.5.9 to 5.5.12
Hi
Yes, I've had a similar problem in that with 5.5.12 various
framework-related APIs such Spring and OSCache which *were*
t was dismissed as
being my imagination by Remy.
Cheers, Allistair
-Original Message-
From: Rick [mailto:[EMAIL PROTECTED]
Sent: 14 November 2005 15:36
To: 'Tomcat Users List'
Subject: Log4j issues upgrading from 5.5.9 to 5.5.12
REPOST: Just wondering if anyone else has seen thi
REPOST: Just wondering if anyone else has seen this issue.
After upgrading from 5.5.9 to 5.5.12, all the same log4j.properties files, I
now have some web-app level classes that I can not catch in my web-app log4j
logger. I ended up having to put loggers in my
common/classes/log4j.properties file
After upgrading from 5.5.9 to 5.5.12, all the same log4j.properties files, I
now have some web-app level classes that I can not catch in my web-app log4j
logger. I ended up having to put loggers in my
common/classes/log4j.properties file to deal with them.
Again, this worked normally in 5.5.9 with
