Return-Path: Delivered-To: apmail-tomcat-dev-archive@www.apache.org Received: (qmail 61806 invoked from network); 13 Feb 2007 02:32:50 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 13 Feb 2007 02:32:50 -0000 Received: (qmail 40135 invoked by uid 500); 13 Feb 2007 02:32:50 -0000 Delivered-To: apmail-tomcat-dev-archive@tomcat.apache.org Received: (qmail 40071 invoked by uid 500); 13 Feb 2007 02:32:50 -0000 Mailing-List: contact dev-help@tomcat.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: "Tomcat Developers List" Delivered-To: mailing list dev@tomcat.apache.org Received: (qmail 40060 invoked by uid 500); 13 Feb 2007 02:32:50 -0000 Delivered-To: apmail-jakarta-tomcat-dev@jakarta.apache.org Received: (qmail 40057 invoked by uid 99); 13 Feb 2007 02:32:50 -0000 Received: from herse.apache.org (HELO herse.apache.org) (140.211.11.133) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 12 Feb 2007 18:32:50 -0800 X-ASF-Spam-Status: No, hits=-9.4 required=10.0 tests=ALL_TRUSTED,NO_REAL_NAME X-Spam-Check-By: apache.org Received: from [140.211.11.4] (HELO brutus.apache.org) (140.211.11.4) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 12 Feb 2007 18:32:42 -0800 Received: by brutus.apache.org (Postfix, from userid 33) id 8E9977142F4; Mon, 12 Feb 2007 18:32:22 -0800 (PST) From: bugzilla@apache.org To: tomcat-dev@jakarta.apache.org Subject: DO NOT REPLY [Bug 32017] - Tomcat 5.5 manager fails to undeploy Struts app In-Reply-To: X-Bugzilla-Reason: AssignedTo Message-Id: <20070213023222.8E9977142F4@brutus.apache.org> Date: Mon, 12 Feb 2007 18:32:22 -0800 (PST) X-Virus-Checked: Checked by ClamAV on apache.org 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=32017 markt@apache.org changed: What |Removed |Added ---------------------------------------------------------------------------- Status|REOPENED |NEEDINFO ------- Additional Comments From markt@apache.org 2007-02-12 18:32 ------- To date, the anti-locking attributes have resolved the locking issues identified by users. It is possible that you have a use case that these don't work for. It is also possible that something you are doing in your web application is causing the problem. To get to the root cause of this issue, sufficient information to reproduce it is required. At the moment there is not enough information in this report to enable the issue to be reproduced. Please provide one of the following: - step by step instructions how to reproduce this from a clean Tomcat install - a WAR that when deployed on a clean install demonstrates the issue -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee. --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org For additional commands, e-mail: dev-help@tomcat.apache.org