Hola, I'm forwarding this to commons-dev to include the commons-logging developers on this discussion. What do you guys think? Is there another readily available key to use when caching LogFactory objects? Or perhaps a way for commons-logging to not cache these, or maybe discard the cache when a webapp (or its classloader, more likely) is shut down?
Yoav Shapira Millennium Research Informatics >-----Original Message----- >From: Ceki Gülcü [mailto:[EMAIL PROTECTED] >Sent: Thursday, August 05, 2004 10:47 AM >To: Log4J Users List >Cc: [EMAIL PROTECTED] >Subject: RE: log4j SEVERE ThreadDeath in Tomcat 5.0.25 > >At 04:22 PM 8/5/2004, Andy McBride wrote: >>Commons logging seems to cache LogFactory instances using its >>classloader as a key - perhaps this could be suspect? > >Oh, yes indeed. > > >-- >Ceki Gülcü > > For log4j documentation consider "The complete log4j manual" > ISBN: 2970036908 http://www.qos.ch/shop/products/clm_t.jsp > > > >--------------------------------------------------------------------- >To unsubscribe, e-mail: [EMAIL PROTECTED] >For additional commands, e-mail: [EMAIL PROTECTED] This e-mail, including any attachments, is a confidential business communication, and may contain information that is confidential, proprietary and/or privileged. This e-mail is intended only for the individual(s) to whom it is addressed, and may not be saved, copied, printed, disclosed or used by anyone else. If you are not the(an) intended recipient, please immediately delete this e-mail from your computer system and notify the sender. Thank you. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
