tomcat-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 26372] - java.lang.ThreadDeath when trying to reload an application
Date Sat, 10 Dec 2005 14:56:49 GMT
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=26372>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=26372


darryl@darrylmiles.org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |darryl@darrylmiles.org




------- Additional Comments From darryl@darrylmiles.org  2005-12-10 15:56 -------
(In reply to comment #37)
> i think i know how to reproduce and prevent this error.  assistance from the
> tomcat developers could enhance the workaround.

I would disagree, your suggestion simply masks your own problem.

Logging isn't the only culprit in the world, and your solution only touches (and
loads) those segments of the logging infrastructure it uses at that time for
that message.


What TC could do to help the developer is improve that ThreadDeath message and
help the developer identify the exact thread of execution (by name and thread
id) and the class it was trying to load at the time.  This feels like a step in
the right direction it helps the developers stamp out their bugs and does not
encrouch into an ugly half-baked solution the maintainers rightfully want to
keep out.


I'm still toying with the idea of keeping generation(s) of WebAppClassLoader's
around, this idea does have merit for me especially when you keep generations of
all modifications to the web-app around (between container restarts) there are
other good side effects too like hot JAR replace on Win32 where JAR locking
might be an issue.  But this sort of development process has to be driven from
an IDE.


-- 
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org


Mime
View raw message