Return-Path: Delivered-To: apmail-jakarta-tomcat-dev-archive@apache.org Received: (qmail 88648 invoked from network); 7 Feb 2002 16:39:21 -0000 Received: from unknown (HELO nagoya.betaversion.org) (192.18.49.131) by daedalus.apache.org with SMTP; 7 Feb 2002 16:39:21 -0000 Received: (qmail 16365 invoked by uid 97); 7 Feb 2002 16:39:14 -0000 Delivered-To: qmlist-jakarta-archive-tomcat-dev@jakarta.apache.org Received: (qmail 16324 invoked by uid 97); 7 Feb 2002 16:39:13 -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 16309 invoked by uid 50); 7 Feb 2002 16:39:12 -0000 Date: 7 Feb 2002 16:39:12 -0000 Message-ID: <20020207163912.16308.qmail@nagoya.betaversion.org> From: bugzilla@apache.org To: tomcat-dev@jakarta.apache.org Cc: Subject: DO NOT REPLY [Bug 6301] - Streams returned by getResourceAsStream don't close properly 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=6301 Streams returned by getResourceAsStream don't close properly remm@apache.org changed: What |Removed |Added ---------------------------------------------------------------------------- Status|REOPENED |RESOLVED Resolution| |WORKSFORME ------- Additional Comments From remm@apache.org 2002-02-07 16:39 ------- I thought your complaint was about the stream not being automatically closed or something like it (which is not the case; if you call close on the IS, it will really close it). Here, you're running into a caching problem, where the cache of the directory context doen't always get revalidated. You can use a Resources element (child of a Context element) in server.xml to disable the cache or tweak it, so that it would do revalidation on each request (although I didn't document that yet, unfortunately; setting the "cacheTTL" property to "-1" should do that; disabling the content caching by setting "cacheObjectMaxSize" to "-1" would also do it): http://jakarta.apache.org/tomcat/tomcat-4.0-doc/config/resources.html -- To unsubscribe, e-mail: For additional commands, e-mail: