Return-Path: Delivered-To: apmail-ws-axis-dev-archive@www.apache.org Received: (qmail 5191 invoked from network); 13 Aug 2007 14:06:51 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 13 Aug 2007 14:06:51 -0000 Received: (qmail 82431 invoked by uid 500); 13 Aug 2007 14:06:43 -0000 Delivered-To: apmail-ws-axis-dev-archive@ws.apache.org Received: (qmail 82376 invoked by uid 500); 13 Aug 2007 14:06:43 -0000 Mailing-List: contact axis-dev-help@ws.apache.org; run by ezmlm Precedence: bulk Reply-To: axis-dev@ws.apache.org list-help: list-unsubscribe: List-Post: List-Id: Delivered-To: mailing list axis-dev@ws.apache.org Received: (qmail 82365 invoked by uid 99); 13 Aug 2007 14:06:43 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 13 Aug 2007 07:06:43 -0700 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of Tony.Dean@sas.com designates 149.173.6.152 as permitted sender) Received: from [149.173.6.152] (HELO mercav04.na.sas.com) (149.173.6.152) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 13 Aug 2007 14:06:37 +0000 Received: from MERCMBX07.na.sas.com ([10.16.9.157]) by mercav04.na.sas.com with InterScan Message Security Suite; Mon, 13 Aug 2007 10:06:16 -0400 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: quoted-printable Subject: [axis2] jboss JARLocking Date: Mon, 13 Aug 2007 10:06:15 -0400 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: [axis2] jboss JARLocking Thread-Index: AcfdsxzcYVRoQfEERFKG8OtPTXJWBw== From: "Tony Dean" To: X-Virus-Checked: Checked by ClamAV on apache.org Hi, When deploying AAR into Jboss containter, you cannot subsequently delete it without first stopping Jboss because of file locking (I suppose hot-update will fail as well). If I deploy an exploded AAR, the issue does not exists. I found a Jboss/Tomcat blog on antiJARLocking, but that did not work. Any ideas from Axis2 developers how to get around this issue? Thanks. Tony Dean SAS Institute Inc. 919.531.6704 tony.dean@sas.com SAS... The Power to Know http://www.sas.com --------------------------------------------------------------------- To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org For additional commands, e-mail: axis-dev-help@ws.apache.org