Return-Path: Delivered-To: apmail-jakarta-tomcat-dev-archive@www.apache.org Received: (qmail 96114 invoked from network); 3 Nov 2003 01:29:20 -0000 Received: from daedalus.apache.org (HELO mail.apache.org) (208.185.179.12) by minotaur-2.apache.org with SMTP; 3 Nov 2003 01:29:20 -0000 Received: (qmail 10445 invoked by uid 500); 3 Nov 2003 01:28:58 -0000 Delivered-To: apmail-jakarta-tomcat-dev-archive@jakarta.apache.org Received: (qmail 10398 invoked by uid 500); 3 Nov 2003 01:28:57 -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 10385 invoked from network); 3 Nov 2003 01:28:57 -0000 Received: from unknown (HELO exchange.sun.com) (192.18.33.10) by daedalus.apache.org with SMTP; 3 Nov 2003 01:28:57 -0000 Received: (qmail 13999 invoked by uid 50); 3 Nov 2003 01:29:04 -0000 Date: 3 Nov 2003 01:29:04 -0000 Message-ID: <20031103012904.13998.qmail@nagoya.betaversion.org> From: bugzilla@apache.org To: tomcat-dev@jakarta.apache.org Cc: Subject: DO NOT REPLY [Bug 24238] - Tomcat WIndows service very slow to stop (delay > 1 minute) X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: minotaur-2.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=24238 Tomcat WIndows service very slow to stop (delay > 1 minute) ------- Additional Comments From paul@tourplan.com 2003-11-03 01:29 ------- This happens when I start Tomcat then immediately stop it, so it's hard to see that it would be spending a lot of time persisting sessions. Also, the fact that Tomcat doesn't seem to be doing anything in this period (based on taskmgr info) and the fact that there is nothing in the logs, would tend to indicate that it isn't persisting session info. It's almost as if it sits there until a 60 second timeout finishes (this timeout could be in Tomcat, or could be in the Windows services manager). Should I be looking to turn up the logging level to see whether that helps? If so, what's the best way to do this? Cheers, Paul. --------------------------------------------------------------------- To unsubscribe, e-mail: tomcat-dev-unsubscribe@jakarta.apache.org For additional commands, e-mail: tomcat-dev-help@jakarta.apache.org