Return-Path: Delivered-To: apmail-ws-axis-user-archive@www.apache.org Received: (qmail 54940 invoked from network); 20 Jan 2010 12:11:16 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 20 Jan 2010 12:11:16 -0000 Received: (qmail 34897 invoked by uid 500); 20 Jan 2010 12:11:14 -0000 Delivered-To: apmail-ws-axis-user-archive@ws.apache.org Received: (qmail 34815 invoked by uid 500); 20 Jan 2010 12:11:14 -0000 Mailing-List: contact axis-user-help@ws.apache.org; run by ezmlm Precedence: bulk Reply-To: axis-user@ws.apache.org list-help: list-unsubscribe: List-Post: List-Id: Delivered-To: mailing list axis-user@ws.apache.org Received: (qmail 34806 invoked by uid 99); 20 Jan 2010 12:11:14 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 20 Jan 2010 12:11:14 +0000 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_HELO_PASS,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of lists@nabble.com designates 216.139.236.158 as permitted sender) Received: from [216.139.236.158] (HELO kuber.nabble.com) (216.139.236.158) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 20 Jan 2010 12:11:04 +0000 Received: from isper.nabble.com ([192.168.236.156]) by kuber.nabble.com with esmtp (Exim 4.63) (envelope-from ) id 1NXZOV-0000TO-Uh for axis-user@ws.apache.org; Wed, 20 Jan 2010 04:10:43 -0800 Message-ID: <27240717.post@talk.nabble.com> Date: Wed, 20 Jan 2010 04:10:43 -0800 (PST) From: macima To: axis-user@ws.apache.org Subject: Hot Update doen't fire ServiceLifeCycle.shutDown() MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Nabble-From: mark@markmaciver.com X-Virus-Checked: Checked by ClamAV on apache.org I've implemented the ServiceLifeCycle interface to create and close connections in the startUp and shutDown methods. shutDown is fired when Tomcat is shutdown, however it isn't fired when I perform a hot update (i.e drop a new version of the aar file into the services directory). Is this by design? If so, is there a way to fire cleanup code when an arr is "hot updated". I'm running Axis 1.5 and Tomcat 5.5.23. Thanks Mark Mac -- View this message in context: http://old.nabble.com/Hot-Update-doen%27t-fire-ServiceLifeCycle.shutDown%28%29-tp27240717p27240717.html Sent from the Axis - User mailing list archive at Nabble.com.