Hi, Not at all no. I did find that another way around it was to pull out log4j.properties from the webapp's classes folder and into WEB-INF and then to use a custom context listener to use BasicConfigurator to load the properties config yourself. And make sure the context listener is the first 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 <cry>. Thanks for confirming I'm not crazy. Were you able to find anything in the changelog between 5.5.9 and .12 that would have caused this? I have not had any luck yet. -Rick -----Original Message----- From: Allistair Crossley [mailto:[EMAIL PROTECTED] Posted At: Monday, 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* configured using a WEB-INF/classes/log4j.properties config in 5.5.9 and less no longer logged. I kind of linked the problem to the fact that these APIs had related ContextListeners in action, and so the logging configuration needed to be available at the time the webapp was started by Tomcat. To fix it, I had to create a separate log4j.properties in common/classes like yourself which is not ideal from my POV. I reported this to the list and to BugZilla, but it 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 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 to deal with them. Again, this worked normally in 5.5.9 with the same configuration. One example, handling OSCache log entries.. -------------------------------------------------- log4j.logger.org.jgroups=INFO, CACHE log4j.logger.com.opensymphony=WARN, CACHE log4j.appender.CACHE=org.apache.log4j.RollingFileAppender log4j.appender.CACHE.File=${catalina.home}/logs/cache.log ... --------------------------------------------------- The Jars for JGroups and OSCache are both in my web-app's lib folder, not in common/lib. But I'm forced to create loggers in common/lib to catch the log entries. My webapp level loggers do not see any log entries from the above mentioned classes. Anyone else have a similar issue and find a fix? Thanks, Rick --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] <FONT SIZE=1 FACE="VERDANA,ARIAL" COLOR=BLUE> ------------------------------------------------------- QAS Ltd. Registered in England: No 2582055 Registered in Australia: No 082 851 474 ------------------------------------------------------- </FONT> <FONT SIZE=1 FACE="VERDANA,ARIAL" COLOR=BLACK> Disclaimer: The information contained within this e-mail is confidential and may be privileged. This email is intended solely for the named recipient only; if you are not authorised you must not disclose, copy, distribute, or retain this message or any part of it. If you have received this message in error please contact the sender at once so that we may take the appropriate action and avoid troubling you further. Any views expressed in this message are those of the individual sender. QAS Limited has the right lawfully to record, monitor and inspect messages between its employees and any third party. Your messages shall be subject to such lawful supervision as QAS Limited deems to be necessary in order to protect its information, its interests and its reputation. Whilst all efforts are made to safeguard Inbound and Outbound emails, QAS Limited cannot guarantee that attachments are virus free or compatible with your systems and does not accept any liability in respect of viruses or computer problems experienced. </FONT> --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
