logging-log4j-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Shapira, Yoav" <Yoav.Shap...@mpi.com>
Subject RE: log4j SEVERE ThreadDeath in Tomcat 5.0.25
Date Thu, 05 Aug 2004 13:32:26 GMT

Hi,
Creating each developer a separate instance is pretty much the only way to go.  That's not
just true for tomcat, but in general.  The alternative always leads to instability and worse
in my experience.  So I'm glad you've done that now.

As for helping further: you nailed it on the head when you say "I wish I could put together
a use case for you" -- that would be ideal.  Bugzilla items without a reproducible test case
tend to receive the least attention and time.  That's not to say the bug doesn't exit.  It's
just a reflection of the fact we (I have my Tomcat Developer hat on when writing this message)
have a ton of work and very little spare bandwidth.

One thing I'll tell you right now, and it's good: the classloaders and application deployers
(including hot swap and runtime restarting of applications) are receiving a thorough refactoring/redesign/re-evaluation
for Tomcat 5.1.  It's the major item Remy has been working on for a month now, with the objective
of coming up with far simpler and far more robust and consistent mechanism.  So there's hope
;)

Yoav Shapira
Millennium Research Informatics


>-----Original Message-----
>From: Allistair Crossley [mailto:Allistair.Crossley@QAS.com]
>Sent: Thursday, August 05, 2004 9:28 AM
>To: Log4J Users List
>Cc: tomcat-user@jakarta.apache.org
>Subject: RE: log4j SEVERE ThreadDeath in Tomcat 5.0.25
>
>Excellent :) I have tried everything in the bugs that relate to this
>issue..
>
>http://nagoya.apache.org/bugzilla/show_bug.cgi?id=26372
>http://issues.apache.org/bugzilla/show_bug.cgi?id=27371
>
>but it's still occurring. I wish I could put together a use case for you
>but 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
>and some days all developers are getting it.
>
>i ended up creating each developer a separate tomcat development instance
>but 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
>>
>>
>>
>> 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
>> tomcat-dev@jakarta.apache.org 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
>>
>>
>> >-----Original Message-----
>> >From: Ceki Gülcü [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
>> than log4j and
>> >unrelated to the well-known configureAndWatch bug in log4j.
>> >
>> >See bug 27371
>> >http://issues.apache.org/bugzilla/show_bug.cgi?id=27371
>> >
>> >In particular, see comments by Claudio Corsi dated 2nd of
>> 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
>> 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
>> >>
>> org.apache.commons.logging.impl.Log4JLogger.error(Log4JLogger.
>> java:195)
>> >>         at
>> >>
>> >org.apache.catalina.session.StandardManager.start(StandardMan
>> ager.java:659)
>> >>         at
>> >>
>> 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
>> developer compiles
>> >>classes to Tomcat which makes Tomcat restart the context.
>> Mostly, because
>> >>sometimes it is fine. We cannot establish a concrete
>> pattern of behaviour
>> >>except that some compiles of any class type that make TC
>> reload the webapp
>> >>cause this unercoverable error.
>> >>
>> >>This has happened with log4j1.2.8 and 1.3alpha0
>> >>
>> >>Cheers, ADC
>> >>
>> >>
>> >><FONT SIZE=1 FACE="VERDANA,ARIAL" COLOR=BLUE>
>> >>-------------------------------------------------------
>> >>QAS Ltd.
>> >>Developers of QuickAddress Software
>> >><a href="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ülcü
>> >
>> >      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
>>
>>
>>
>>
>> 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: log4j-user-unsubscribe@logging.apache.org
>> For additional commands, e-mail: log4j-user-help@logging.apache.org
>>
>>
>
>
><FONT SIZE=1 FACE="VERDANA,ARIAL" COLOR=BLUE>
>-------------------------------------------------------
>QAS Ltd.
>Developers of QuickAddress Software
><a href="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




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: log4j-user-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-user-help@logging.apache.org


Mime
View raw message