You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@commons.apache.org by "Bernd Eckenfels (JIRA)" <ji...@apache.org> on 2015/07/24 20:28:04 UTC
[jira] [Updated] (VFS-574) warning about not closed
OperationProviders when calling DefaultFilesystemManager.close
[ https://issues.apache.org/jira/browse/VFS-574?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Bernd Eckenfels updated VFS-574:
--------------------------------
Attachment: vfs-closeop.diff
Good catch. Could you maybe check if the following patch helps the situation?
> warning about not closed OperationProviders when calling DefaultFilesystemManager.close
> ---------------------------------------------------------------------------------------
>
> Key: VFS-574
> URL: https://issues.apache.org/jira/browse/VFS-574
> Project: Commons VFS
> Issue Type: Bug
> Affects Versions: 2.1
> Reporter: Vladimir Tsanev
> Assignee: Bernd Eckenfels
> Priority: Minor
> Attachments: vfs-closeop.diff
>
>
> I see a warning on application shutdown.
> {code}
> WARN : DefaultFilesystemManager.close: not all components are closed: [com.intridea.io.vfs.provider.s3.operations.S3FileOperationsProvider@30b544a5]
> {code}
> I am using common-vfs2 version 2.1.1660580.1 and an s3 provider is on the classpath that defines a OperationProvider implementation.
> looking at the code seems that operation providers are added in components collection on setup, but closeCompoent is not invoked for operation providers on close().
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)