[jira] [Commented] (VFS-253) AbstractFileObject: wrong synchronization of content-related code

["Daryl Odnert (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/VFS-253?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16699609#comment-16699609 ] 

Daryl Odnert commented on VFS-253:
----------------------------------

I opened a new bug today requesting that the API documentation is fixed to identify requirements for multi-threaded applications.

> AbstractFileObject: wrong synchronization of content-related code
> -----------------------------------------------------------------
>
>                 Key: VFS-253
>                 URL: https://issues.apache.org/jira/browse/VFS-253
>             Project: Commons VFS
>          Issue Type: Bug
>    Affects Versions: 2.0
>            Reporter: Marek Zawirski
>            Priority: Major
>
> Creating content through {{AbstractFileObject#getContent()}} and {{DefaultFileContent}} itself seem to be synchronized, but closing the content by {{AbstractFileObject#close()}} and checking whether it is open, by {{AbstractFileObject#isContentOpen()}} are NOT synchronized.
> Both these methods miss some lock-object. For {{close()}} it may result in severe race condition in case of {{FileObject}} shared across more than one thread.
> BTW, thead-safeness of important VFS classes/interfaces like {{FileObject}} is not documented in javadoc.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)