You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@commons.apache.org by "Mario Ivankovits (JIRA)" <ji...@apache.org> on 2007/03/19 20:49:32 UTC

[jira] Resolved: (VFS-112) Deadlock when a FileMonitor fires an event and another thread deletes a file at the same time

     [ https://issues.apache.org/jira/browse/VFS-112?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Mario Ivankovits resolved VFS-112.
----------------------------------

       Resolution: Fixed
    Fix Version/s: 1.1

Thanks!

I slightly changed the patch to avoid the additional creation of the ArrayList. I think it should do it too, please give it a try.

Ciao,
Mario

> Deadlock when a FileMonitor fires an event and another thread deletes a file at the same time
> ---------------------------------------------------------------------------------------------
>
>                 Key: VFS-112
>                 URL: https://issues.apache.org/jira/browse/VFS-112
>             Project: Commons VFS
>          Issue Type: Bug
>            Reporter: Tim Rademacher
>             Fix For: 1.1
>
>         Attachments: AbstractFileSystem.diff
>
>
> Hi!
> I experienced a deadlock when one thread (the DefaultFileMonitor) fires an event in which a file is modified and another thread deletes a file at the same time.
> The first thread first locks the listenerMap to inform all listener and then tries to lock the FileSystem fs to modify the file.
> The second thread first locks the FileSystem fs and then tries to inform all listener by locking the listenerMap.
> I already made a fix, but I don't know, if this affects anything else. 
> Regards
> Tim

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org