Commons logging seems to cache LogFactory instances using its classloader as a key - perhaps this could be suspect?
> -----Original Message----- > From: Ceki G�lc� [mailto:[EMAIL PROTECTED] > Sent: 05 August 2004 14:58 > To: Log4J Users List > Cc: [EMAIL PROTECTED] > Subject: RE: log4j SEVERE ThreadDeath in Tomcat 5.0.25 > > > > In relation to bug #26372 Remy wrote: > > ------- Additional Comments From Remy Maucherat 2004-01-23 > 11:54 ------- > > This is the old issue of log4j trying to use the previous classloader > (reloading > will create a new classloader to load class definitions; see > bug 3888). > Maybe it > would be good to leave this bug open so that people can > complain using it, rather than file duplicates. However, I'd > like everyone to know that the "bug" will never be fixed. You > can probably fix the problem by putting log4 JARs (and the > necessary commons-logging wrapper classes) inside the webapp > repository. > > -------------------------------------------------------------- > ------------- > > Does anyone know what Remy is talking about? When does log4j > try to a use previous classloader? I'd appreciate if someone > could shed some light onto the matter. I am trying to > understand what log4j is doing wrong, if anything, and > correct our mistake. > > > > At 03:17 PM 8/5/2004, you wrote: > > >Hi, > >I see what you mean. The relevant Tomcat code is being significantly > >refactored at the moment for Tomcat 5.1, but I'll try to > look through the > >current version to see if the started/ThreadDeath logic is > changed. I > >also added [EMAIL PROTECTED] as a CC on this bug > item, but > >I've yet to change the Component of the bug to Tomcat. Stay tuned... > > > >Yoav Shapira > >Millennium Research Informatics > > -- > 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] > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
