Details

    • Type: Bug
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 2.0
    • Fix Version/s: 2.1
    • Labels:

      Description

      When creating a org.apache.commons.vfs2.impl.VirtualFileSystem by org.apache.commons.vfs2.impl.VirtualFileProvider it is tracked as a component. But since VirtualFileProvider is not an AbstractFileProvider and not registered in providers it will never be closed by org.apache.commons.vfs2.impl.DefaultFileSystemManager._closeFileSystem(FileSystem). Also the final instance of VirtualFileProvider does not get closed when the DefaultFileSystemManager gets closed.

      VirtualFileSystem itself does not have critical resources, but its DelegatedFiles are cached so there should be a way to close them.

        Attachments

        1. vfs-544-v2.patch
          5 kB
          Bernd Eckenfels

          Activity

            People

            • Assignee:
              b.eckenfels Bernd Eckenfels
              Reporter:
              b.eckenfels Bernd Eckenfels
            • Votes:
              1 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: