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=37218>. 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=37218 ------- Additional Comments From [EMAIL PROTECTED] 2005-10-24 17:07 ------- (In reply to comment #4) > Remy, > > I don't understand what you mean in your last post. How is the error on the > request thread related to the ThreadDeath issue I am seeing? You were the one quoting another user about an irrelevant issue, so I was simply pointing his problem was not the same as your problem. > What I am seeing on my end is that as soon as I get a ThreadDeath from > manager/redeploy then I am forced to restart the entire container (not only > the > webapp). If I try to stop, then start the webapp without a full container > restart, I get another fatal error. > > Surely you don't expect us to restart the entire container every time we make > an > application modification? On my end this can take up to 60 seconds, making > development unbearable. Yes, if you mess with the classloading and it ends up in an unpredictable state, I expect you to restart the container. If you don't like it, then try to find another, hopefully more robust, container, as I don't know how to make Tomcat more robust for classloading handling. As this is going nowhere (as with most of the bug reports you are involved with, I have to note), this will be my last reply. -- 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: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
