Return-Path: X-Original-To: apmail-axis-java-dev-archive@www.apache.org Delivered-To: apmail-axis-java-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 8A5EB118E1 for ; Fri, 29 Aug 2014 10:39:54 +0000 (UTC) Received: (qmail 58054 invoked by uid 500); 29 Aug 2014 10:39:54 -0000 Delivered-To: apmail-axis-java-dev-archive@axis.apache.org Received: (qmail 57909 invoked by uid 500); 29 Aug 2014 10:39:53 -0000 Mailing-List: contact java-dev-help@axis.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: java-dev@axis.apache.org Delivered-To: mailing list java-dev@axis.apache.org Received: (qmail 57899 invoked by uid 99); 29 Aug 2014 10:39:53 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 29 Aug 2014 10:39:53 +0000 Date: Fri, 29 Aug 2014 10:39:53 +0000 (UTC) From: =?utf-8?Q?Thorsten_Sch=C3=B6ning_=28JIRA=29?= To: java-dev@axis.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (AXIS2-4094) Jars are locked in the file system even after undeployment of the axis2 webapp MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/AXIS2-4094?page=3Dcom.atlassian= .jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=3D1411= 5096#comment-14115096 ]=20 Thorsten Sch=C3=B6ning commented on AXIS2-4094: ------------------------------------------ I have the same issue with current Tomcat 7 and Axis2 1.6.2: Even if I stop= the Axis2 service the jars in the lib dirs of the distinct services stay l= ocked and can't be replaced. Things like telling Tomcat not to lock jars di= dn't work for me, so I guess it's really Axis2 locking things and Tomcat si= mply doesn't know about it. https://confluence.sakaiproject.org/display/BOOT/Avoiding+JAR+and+file+lock= ing+under+Windows http://tomcat.apache.org/tomcat-7.0-doc/config/context.html#Standard%20Impl= ementation As a workaround one can use the "Find leaks" button in the bottom of the To= mcat manager app, which triggers a full garbage collection. After hitting t= hat button Axis2 seems to get completely unloaded from memory and all locke= d files are unlocked. Sometimes Tomcat notes that Axis2 leaked memory even = if it has been stopped, sometimes not... Luckily this functionality is avai= lable for ANT as well, if you need to automatically deploy some Axis2 servi= ces, like I do: http://tomcat.apache.org/tomcat-7.0-doc/api/org/apache/catalina/ant/FindLea= ksTask.html =09 =09 =09 =09 =09=09 =09=09=09 =09=09 =09 =09 =09=09 =09 =09 =09=09 =09=09 =09 > Jars are locked in the file system even after undeployment of the axis2 w= ebapp > -------------------------------------------------------------------------= ----- > > Key: AXIS2-4094 > URL: https://issues.apache.org/jira/browse/AXIS2-4094 > Project: Axis2 > Issue Type: Bug > Components: deployment > Affects Versions: 1.4, 1.4.1 > Environment: WinXP, Tomcat 4.1, Tomcat 5.5, Tomcat 6, WebSphere 6= .0 & 6.1, Glassfish 2, > Reporter: Michael Heemskerk > Assignee: Deepal Jayasinghe > > Webapp containing axis2 servlet cannot be succesfuly undeployed because j= ar files in WEB-INF/lib are locked and cannot be deleted until the servlet = container is stopped. -- This message was sent by Atlassian JIRA (v6.2#6252) --------------------------------------------------------------------- To unsubscribe, e-mail: java-dev-unsubscribe@axis.apache.org For additional commands, e-mail: java-dev-help@axis.apache.org