tomcat-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 10026] - manager/stop and manager/remove
Date Fri, 13 Jun 2003 18:35:57 GMT
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=10026>.
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 remm@apache.org  2003-06-13 18:35 -------
I have specifically investigated this problem during the past few days, and can
draw the same conclusions. There's unfortunately little or nothing that Tomcat
can do.

Here's what happens:
- XML paser uses get resource to load the DTD
- Tomcat returns a jar:file: URL, as the DTD is inside a JAR
- XML parser does read from that without setting setUseCaches(false), so this
causes the JAR to be locked until the VM is terminated

Tomcat cannot do anything about it, unless we add custom code in getResource to
handle non class resources (ex: we could extract the resource to teh work dir,
and return a file URL to there). AFAIK, there's nothing which forbids that, so
I'll experiment with doing that in TC 5.

---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-dev-help@jakarta.apache.org


Mime
View raw message