Return-Path: Delivered-To: apmail-jakarta-tomcat-dev-archive@apache.org Received: (qmail 63702 invoked from network); 13 Jun 2003 18:12:32 -0000 Received: from exchange.sun.com (192.18.33.10) by daedalus.apache.org with SMTP; 13 Jun 2003 18:12:32 -0000 Received: (qmail 18797 invoked by uid 97); 13 Jun 2003 18:14:52 -0000 Delivered-To: qmlist-jakarta-archive-tomcat-dev@nagoya.betaversion.org Received: (qmail 18790 invoked from network); 13 Jun 2003 18:14:52 -0000 Received: from daedalus.apache.org (HELO apache.org) (208.185.179.12) by nagoya.betaversion.org with SMTP; 13 Jun 2003 18:14:52 -0000 Received: (qmail 62909 invoked by uid 500); 13 Jun 2003 18:12:23 -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 62896 invoked from network); 13 Jun 2003 18:12:23 -0000 Received: from exchange.sun.com (192.18.33.10) by daedalus.apache.org with SMTP; 13 Jun 2003 18:12:23 -0000 Received: (qmail 18770 invoked by uid 50); 13 Jun 2003 18:14:43 -0000 Date: 13 Jun 2003 18:14:43 -0000 Message-ID: <20030613181443.18769.qmail@nagoya.betaversion.org> From: bugzilla@apache.org To: tomcat-dev@jakarta.apache.org Cc: Subject: DO NOT REPLY [Bug 10026] - manager/stop and manager/remove X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: daedalus.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://nagoya.apache.org/bugzilla/show_bug.cgi?id=10026 manager/stop and manager/remove ------- Additional Comments From sys@yahoo.com 2003-06-13 18:14 ------- A similar bug was fixed in Log4J. While it's arguable whether it's a struts bug, tomcat bug, or a windows bug, I thought I'd post the details to see if anyone has ideas on how tomcat can fix this. The bug (from what I understand) is that when dtd's are loaded from the jar (while running on windows), the jar is locked b/c the input stream for the dtd has not be properly closed. In log4j, this is fixed by using a custom EntityResolver to load the dtd. (the resolver makes a copy of the dtd input stream in memory and return the copied stream after closing the real input stream) references to this can be found in the log4j code, but this url from the barracuda project has a pretty good summary: http://barracuda.enhydra.org/software/cvs/cvsweb.cgi/Projects/EnhydraOrg/toolsT ech/Barracuda/WEB-INF/lib/log4j-1.2.7a.jar?rev=1.1&content-type=text/x-cvsweb- markup the files of interest in log4j are: org/apache/log4j/xml/Log4jEntityResolver.java org/apache/log4j/xml/DOMConfigurator.java is there some way for tomcat to always use a custom EntityResolver if the system is windows? Something that may also be of interest: I've found that if I expand the jar and dump all the files into WEB- INF/classes, there are problems undeploy/removing the app --------------------------------------------------------------------- To unsubscribe, e-mail: tomcat-dev-unsubscribe@jakarta.apache.org For additional commands, e-mail: tomcat-dev-help@jakarta.apache.org