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=27371>. 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=27371 ------- Additional Comments From [EMAIL PROTECTED] 2005-11-07 07:11 ------- Brett, There seems to be a mismatch between your test-case description and what I've been experiencing on my end. What I see on my end is request #1 is run to termination, I request a reload of the webapp, Tomcat's manager fails the reload operation and indicates a ThreadDeath has occured. I fully expect the request to get ThreadDeath if it continues running beyond the scope of a context reload but what I am seeing (and I consider this a bug) is Tomcat dishing out a ThreadDeath to a completely unrelated request. If I try sending out request #2 after the reload operation returns ThreadDeath, the request will fail with yet another exception. From this point onward Tomcat is in some sort of bad state and no matter how many times I try manager stop/start/reload it'll always fail. I am forced to fully shutdown Tomcat and restart it. New requests to the webapp now work. You can read more about this here: http://www.netbeans.org/issues/show_bug.cgi?id=62529 Do you have any idea why this is occuring? I have been unable to narrow this down to a minimal testcase. I saw it once in my minimal testcase, but too rare to be of any use. In my original application I see it on the first manager/reload request. I will continue trying to isolate the problem. -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
