[
https://issues.apache.org/jira/browse/VFS-752?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17010803#comment-17010803
]
Bernd Eckenfels commented on VFS-752:
-------------------------------------
We might also need a different close method on FileObject, because the current
one only closes the thread local part of file content and then forgets the
filecontent so it can never be closed for the other threads.
But I think this severity can be scaled down, it should be unlikely that the
provider instead of the Filesystem is closed (because that would have a lot of
splash damage in multithreaded apps).
> AbstractFileProvider close should close all fileSystems before clearing the
> cache
> ---------------------------------------------------------------------------------
>
> Key: VFS-752
> URL: https://issues.apache.org/jira/browse/VFS-752
> Project: Commons VFS
> Issue Type: Bug
> Affects Versions: 2.5.0
> Reporter: Harald Kuhn
> Priority: Major
>
> The close method of AbstractFileProvider currently only clears the cache of
> FileSystem references without closing them first. This can cause open
> connections (e.g. with the SFTPProvider) if each FileSystem is not
> explicitly closed via closeFileSystem. This is a bit error prone.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
