Return-Path: Delivered-To: apmail-jakarta-tomcat-dev-archive@www.apache.org Received: (qmail 92700 invoked from network); 15 Jul 2004 07:02:11 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur-2.apache.org with SMTP; 15 Jul 2004 07:02:11 -0000 Received: (qmail 82872 invoked by uid 500); 15 Jul 2004 07:02:01 -0000 Delivered-To: apmail-jakarta-tomcat-dev-archive@jakarta.apache.org Received: (qmail 82814 invoked by uid 500); 15 Jul 2004 07:02:00 -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 82797 invoked by uid 99); 15 Jul 2004 07:02:00 -0000 X-ASF-Spam-Status: No, hits=1.1 required=10.0 tests=NO_REAL_NAME,UPPERCASE_25_50 X-Spam-Check-By: apache.org Received: from [192.18.33.10] (HELO exchange.sun.com) (192.18.33.10) by apache.org (qpsmtpd/0.27.1) with SMTP; Thu, 15 Jul 2004 00:02:00 -0700 Received: (qmail 6129 invoked by uid 50); 15 Jul 2004 07:03:22 -0000 Date: 15 Jul 2004 07:03:22 -0000 Message-ID: <20040715070322.6128.qmail@nagoya.betaversion.org> From: bugzilla@apache.org To: tomcat-dev@jakarta.apache.org Cc: Subject: DO NOT REPLY [Bug 29286] - Undeploy App does not delete WAR file X-Virus-Checked: Checked 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://issues.apache.org/bugzilla/show_bug.cgi?id=29286 Undeploy App does not delete WAR file ------- Additional Comments From remm@apache.org 2004-07-15 07:03 ------- I think this is useful information (I'm still as tried of these locking issues, though ;) ). Normally in such cases, using setUseCaches on the URL connection fixes it. If this doesn't work for some reason (it could be there's another lock somewhere), then I don't know how to fix it. I'm planning a deployer refactoring in the next release, as right now it's become too complex to maintain. --------------------------------------------------------------------- To unsubscribe, e-mail: tomcat-dev-unsubscribe@jakarta.apache.org For additional commands, e-mail: tomcat-dev-help@jakarta.apache.org