Return-Path: Delivered-To: apmail-xml-cocoon-dev-archive@xml.apache.org Received: (qmail 93712 invoked by uid 500); 10 Oct 2001 16:58:48 -0000 Mailing-List: contact cocoon-dev-help@xml.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: list-post: Reply-To: cocoon-dev@xml.apache.org Delivered-To: mailing list cocoon-dev@xml.apache.org Received: (qmail 93673 invoked from network); 10 Oct 2001 16:58:47 -0000 Message-ID: <3BC47E7B.5B711D3E@apache.org> Date: Wed, 10 Oct 2001 12:59:39 -0400 From: Berin Loritsch X-Mailer: Mozilla 4.75 [en] (Windows NT 5.0; U) X-Accept-Language: en MIME-Version: 1.0 To: cocoon-users@xml.apache.org, Cocoon Dev Subject: Re: Cocoon locking files on filesystem References: <01101011225906.12980@dj> <20011010173651.06a6f750.sergio.carvalho@acm.org> <0110101846210L.12980@dj> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N Bertrand Delacretaz wrote: > > On Wednesday 10 October 2001 18:36, Sergio Carvalho wrote: > > . . . > > The finalize method of all streams in java > > closes the stream, so it will release the lock. > > > If I remember correctly, the call is System.gc() . . . > > Is this guaranteed to have an effect every time you call it? > AFAIK System.gc() is a *suggestion* to the JVM to run garbage collection, so > it might not work reliably in all environments. If there are any streams that Cocoon retains the lock to, it is because it is not being closed. This should be classified as a bug. If you can reliably reproduce it, it can be traced and fixed. You do need to validate your code to ensure that your code is not causing the issues. I missed the original message, so if you can post the details, I would appreciate it. --------------------------------------------------------------------- To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org For additional commands, email: cocoon-dev-help@xml.apache.org