Return-Path: Delivered-To: apmail-jakarta-tomcat-dev-archive@apache.org Received: (qmail 53179 invoked from network); 12 May 2002 14:28:23 -0000 Received: from unknown (HELO nagoya.betaversion.org) (192.18.49.131) by daedalus.apache.org with SMTP; 12 May 2002 14:28:23 -0000 Received: (qmail 8619 invoked by uid 97); 12 May 2002 14:28:18 -0000 Delivered-To: qmlist-jakarta-archive-tomcat-dev@jakarta.apache.org Received: (qmail 8585 invoked by uid 97); 12 May 2002 14:28:17 -0000 Mailing-List: contact tomcat-dev-help@jakarta.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Help: List-Post: List-Id: "Tomcat Developers List" Reply-To: "Tomcat Developers List" Delivered-To: mailing list tomcat-dev@jakarta.apache.org Received: (qmail 8565 invoked by uid 50); 12 May 2002 14:28:16 -0000 Date: 12 May 2002 14:28:16 -0000 Message-ID: <20020512142816.8564.qmail@nagoya.betaversion.org> From: bugzilla@apache.org To: tomcat-dev@jakarta.apache.org Cc: Subject: DO NOT REPLY [Bug 8935] - Deadlock with reload in manager X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=8935 Deadlock with reload in manager bernhard.maehr@gmx.at changed: What |Removed |Added ---------------------------------------------------------------------------- Priority|Other |Medium ------- Additional Comments From bernhard.maehr@gmx.at 2002-05-12 14:28 ------- I don't think that is normal. As far as I know this method is the common way to write a servlet that outputs infinite output. At least the servlet should leave after a while from trying to stop this servlet so the deadlock would be removed. It should NOT be that the whole server is blocked until killing the process (which can not be done at the most webspace-accounts). -- To unsubscribe, e-mail: For additional commands, e-mail: