Return-Path: Delivered-To: apmail-jakarta-tomcat-dev-archive@apache.org Received: (qmail 86159 invoked from network); 26 Dec 2001 17:56:32 -0000 Received: from unknown (HELO nagoya.betaversion.org) (192.18.49.131) by daedalus.apache.org with SMTP; 26 Dec 2001 17:56:32 -0000 Received: (qmail 1246 invoked by uid 97); 26 Dec 2001 17:56:27 -0000 Delivered-To: qmlist-jakarta-archive-tomcat-dev@jakarta.apache.org Received: (qmail 1210 invoked by uid 97); 26 Dec 2001 17:56:26 -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 1199 invoked from network); 26 Dec 2001 17:56:26 -0000 Message-ID: <003c01c18e36$a06200c0$6501a8c0@apache.org> From: "Remy Maucherat" To: "Tomcat Developers List" References: <20011226110055.28679.qmail@icarus.apache.org> <010401c18e08$db9f5760$6501a8c0@apache.org> <3C2A09BB.56FDB287@voyager.apg.more.net> Subject: Re: cvs commit: jakarta-tomcat-4.0/catalina/src/share/org/apache/catalina/startup Catalina.java Date: Wed, 26 Dec 2001 09:56:16 -0800 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2600.0000 X-Mimeole: Produced By Microsoft MimeOLE V6.00.2600.0000 X-Spam-Rating: localhost.apache.org 1.6.2 0/1000/N X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N > Remy Maucherat wrote: > > > > It does work fine for me. The change is a bad idea anyway, since the > > shutdown is asynchronous (it would be almost equivalent to not attemping to > > shutdown and kill the process). > > > > The way I am using Tomcat isn't typical, the instance that fails to > terminate on shutdown is being used as a stand alone soap server which > uses https. The only web application is the soap server. It doesn't work > in this case. This configuration had worked fine with Tomcat 4.0.1. This > is the first time I tried running the soap server with 4.1-dev, I wanted > to test the DbcpDataSourceFactory. > > I didn't realize that the container stop was asynchronous, so you are > right, using System.exit() like this is not a good solution. If you > look at the code you will notice that the comment says FIX ME ???. :-) > I put the System.exit() in as a temp fix. I don't think it's a good idea to put something in that you know is broken. We might forget about it (esp since there's some vacation to help). > The only cause I can come up with which would prevent the java process > from terminating is if there are still threads running which weren't > terminated by the stop. Hence the speculation that the problem has something > to do with the STM changes. If there's no STM servlets, it shouldn't do that. Also, if you look at the code, I don't see why it would cause some problems. Is it Apache SOAP ? I'll try to look at it if it is. Remy -- To unsubscribe, e-mail: For additional commands, e-mail: