commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 34592] - [VFS] Zip files are locked even after close()
Date Mon, 25 Apr 2005 21:34:28 GMT
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=34592>.
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=34592





------- Additional Comments From anthony.goubard@wanadoo.nl  2005-04-25 23:34 -------
So what you're saying is that if I do (using the example attached to this bug)
jarDir.close();
testJar.close();
System.gc();
// maybe wait
then I should be able to remove or replace the zip file.

Note that I had then another problem related maybe to this bug.
When I replace the Zip file with another file I still have the old content even
if I recreate the FileObject from its URI.
If I remove it from the cache, then I have a empty listing of the directory.
Apparently it still uses the old ZipFileSystem as the getParentLayer() returns
null (this happened probably when I closed the old ZipFileSystem).

Do you know how I could have a FileObject with the new zip file?

-- 
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: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org


Mime
View raw message