Mailing-List: contact log4j-user-help@logging.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Log4J Users List" <log4j-user@logging.apache.org>
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Subject: RE: log4j SEVERE ThreadDeath in Tomcat 5.0.25
Date: Thu, 5 Aug 2004 14:28:13 +0100
Message-ID: <5684A7E6FB10504393A2806C1F4C021003B0DFB9@orion.qas.com>
Thread-Topic: log4j SEVERE ThreadDeath in Tomcat 5.0.25
Thread-Index: AcR66z035iv+eSIKSGSXtFK09lkjmgAAtSqgAABrxMA=
From: "Allistair Crossley" <Allistair.Crossley@QAS.com>
To: "Log4J Users List" <log4j-user@logging.apache.org>
Cc: <tomcat-user@jakarta.apache.org>

Excellent :) I have tried everything in the bugs that relate to this issue..

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=3D26372
http://issues.apache.org/bugzilla/show_bug.cgi?id=3D27371

but it's still occurring. I wish I could put together a use case for you bu=
t the error is so sporadic. One day we can compile the whole day without a =
problem, the next 1 developer gets the ThreadDeath every time he compiles a=
nd some days all developers are getting it.

i ended up creating each developer a separate tomcat development instance b=
ut each developer is getting the problem at different times.

please let me know if I can be of further help in debugging this for you

Cheers, Allistair.


> -----Original Message-----
> From: Shapira, Yoav [mailto:Yoav.Shapira@mpi.com]
> Sent: 05 August 2004 14:17
> To: Log4J Users List
> Subject: RE: log4j SEVERE ThreadDeath in Tomcat 5.0.25
>=20
>=20
>=20
> Hi,
> I see what you mean.  The relevant Tomcat code is being=20
> significantly refactored at the moment for Tomcat 5.1, but=20
> I'll try to look through the current version to see if the=20
> started/ThreadDeath logic is changed.  I also added=20
> tomcat-dev@jakarta.apache.org as a CC on this bug item, but=20
> I've yet to change the Component of the bug to Tomcat.  Stay tuned...
>=20
> Yoav Shapira
> Millennium Research Informatics
>=20
>=20
> >-----Original Message-----
> >From: Ceki G=FClc=FC [mailto:ceki@qos.ch]
> >Sent: Thursday, August 05, 2004 8:55 AM
> >To: Log4J Users List
> >Subject: Re: log4j SEVERE ThreadDeath in Tomcat 5.0.25
> >
> >
> >As far as I can tell, this bug is more of a Tomcat issue=20
> than log4j and
> >unrelated to the well-known configureAndWatch bug in log4j.
> >
> >See bug 27371
> >http://issues.apache.org/bugzilla/show_bug.cgi?id=3D27371
> >
> >In particular, see comments by Claudio Corsi dated 2nd of=20
> August 2004.
> >
> >I hope this helps.
> >
> >
> >
> >At 11:31 AM 8/5/2004, Allistair Crossley wrote:
> >>We are experiencing Tomcat failure as soon as the following=20
> exception gets
> >>thrown;
> >>
> >>SEVERE: Exception invoking periodic operation:
> >>java.lang.ThreadDeath
> >>         at
> >>
> >org.apache.catalina.loader.WebappClassLoader.loadClass(Webapp
> ClassLoader.ja
> >va:1229)
> >>         at
> >>
> >org.apache.catalina.loader.WebappClassLoader.loadClass(Webapp
> ClassLoader.ja
> >va:1189)
> >>         at java.lang.ClassLoader.loadClassInternal(Unknown Source)
> >>         at
> >org.apache.log4j.spi.LoggingEvent.<init>(LoggingEvent.java:241)
> >>         at org.apache.log4j.Category.forcedLog(Category.java:431)
> >>         at org.apache.log4j.Category.log(Category.java:966)
> >>         at
> >>=20
> org.apache.commons.logging.impl.Log4JLogger.error(Log4JLogger.
> java:195)
> >>         at
> >>
> >org.apache.catalina.session.StandardManager.start(StandardMan
> ager.java:659)
> >>         at
> >>=20
> org.apache.catalina.core.StandardContext.start(StandardContext
> .java:4272)
> >>         at
> >>
> >org.apache.catalina.core.StandardContext.reload(StandardConte
> xt.java:3021)
> >>         at
> >>
> >org.apache.catalina.core.StandardContext.backgroundProcess(St
> andardContext.
> >java:4629)
> >>         at
> >>
> >org.apache.catalina.core.ContainerBase$ContainerBackgroundPro
> cessor.process
> >Children(ContainerBase.java:1619)
> >>         at
> >>
> >org.apache.catalina.core.ContainerBase$ContainerBackgroundPro
> cessor.process
> >Children(ContainerBase.java:1628)
> >>         at
> >>
> >org.apache.catalina.core.ContainerBase$ContainerBackgroundPro
> cessor.process
> >Children(ContainerBase.java:1628)
> >>         at
> >>
> >org.apache.catalina.core.ContainerBase$ContainerBackgroundPro
> cessor.run(Con
> >tainerBase.java:1608)
> >>         at java.lang.Thread.run(Unknown Source)
> >>
> >>This exception we have discovered mostly occurs after a=20
> developer compiles
> >>classes to Tomcat which makes Tomcat restart the context.=20
> Mostly, because
> >>sometimes it is fine. We cannot establish a concrete=20
> pattern of behaviour
> >>except that some compiles of any class type that make TC=20
> reload the webapp
> >>cause this unercoverable error.
> >>
> >>This has happened with log4j1.2.8 and 1.3alpha0
> >>
> >>Cheers, ADC
> >>
> >>
> >><FONT SIZE=3D1 FACE=3D"VERDANA,ARIAL" COLOR=3DBLUE>
> >>-------------------------------------------------------
> >>QAS Ltd.
> >>Developers of QuickAddress Software
> >><a href=3D"http://www.qas.com">www.qas.com</a>
> >>Registered in England: No 2582055
> >>Registered in Australia: No 082 851 474
> >>-------------------------------------------------------
> >></FONT>
> >>
> >>
> >>------------------------------------------------------------
> ---------
> >>To unsubscribe, e-mail: log4j-user-unsubscribe@logging.apache.org
> >>For additional commands, e-mail: log4j-user-help@logging.apache.org
> >
> >--
> >Ceki G=FClc=FC
> >
> >      For log4j documentation consider "The complete log4j manual"
> >      ISBN: 2970036908 http://www.qos.ch/shop/products/clm_t.jsp
> >
> >
> >
> >---------------------------------------------------------------------
> >To unsubscribe, e-mail: log4j-user-unsubscribe@logging.apache.org
> >For additional commands, e-mail: log4j-user-help@logging.apache.org
>=20
>=20
>=20
>=20
> This e-mail, including any attachments, is a confidential=20
> business communication, and may contain information that is=20
> confidential, proprietary and/or privileged.  This e-mail is=20
> intended only for the individual(s) to whom it is addressed,=20
> and may not be saved, copied, printed, disclosed or used by=20
> anyone else.  If you are not the(an) intended recipient,=20
> please immediately delete this e-mail from your computer=20
> system and notify the sender.  Thank you.
>=20
>=20
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: log4j-user-unsubscribe@logging.apache.org
> For additional commands, e-mail: log4j-user-help@logging.apache.org
>=20
>=20


<FONT SIZE=3D1 FACE=3D"VERDANA,ARIAL" COLOR=3DBLUE>=20
-------------------------------------------------------
QAS Ltd.
Developers of QuickAddress Software
<a href=3D"http://www.qas.com">www.qas.com</a>
Registered in England: No 2582055
Registered in Australia: No 082 851 474
-------------------------------------------------------
</FONT>


---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-user-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-user-help@logging.apache.org