Return-Path: Delivered-To: apmail-jakarta-tomcat-dev-archive@apache.org Received: (qmail 72536 invoked from network); 1 May 2002 18:50:42 -0000 Received: from unknown (HELO nagoya.betaversion.org) (192.18.49.131) by daedalus.apache.org with SMTP; 1 May 2002 18:50:42 -0000 Received: (qmail 4217 invoked by uid 97); 1 May 2002 18:50:40 -0000 Delivered-To: qmlist-jakarta-archive-tomcat-dev@nagoya.betaversion.org Received: (qmail 4128 invoked by alias); 1 May 2002 18:50:39 -0000 Delivered-To: jakarta-archive-tomcat-dev@jakarta.apache.org Received: (qmail 4092 invoked by uid 97); 1 May 2002 18:50:38 -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 4058 invoked by alias); 1 May 2002 18:50:37 -0000 Date: 1 May 2002 18:50:36 -0000 Message-ID: <20020501185036.4023.qmail@nagoya.betaversion.org> From: bugzilla@apache.org To: tomcat-dev@jakarta.apache.org Cc: Subject: DO NOT REPLY [Bug 8700] - Process stays alive after shutdown 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=8700 Process stays alive after shutdown remm@apache.org changed: What |Removed |Added ---------------------------------------------------------------------------- Severity|Normal |Enhancement ------- Additional Comments From remm@apache.org 2002-05-01 18:50 ------- Catalina doesn't shutdown if there is a non-daemon thread still running. Catalina does clean all its threads correctly, so the VM would exist. If you create threads, you either have to shut them down, or mark them as daemons. I didn't lose hope yet to make that more robust somewhere in the 4.1.x releases. Probably not anytime soon, though. -- To unsubscribe, e-mail: For additional commands, e-mail: