[
https://issues.apache.org/jira/browse/VFS-817?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17508113#comment-17508113
]
Mykhailo commented on VFS-817:
------------------------------
Hello, Gary,
i didn't wrote about changing only one method, i wrote about all methods on
SftpFileObject marked with synchronized with locks on FileSystem in their
logic. Provided example is just to make clear what i meant. This is not a
solution. Unfortunately i have no time as for now to provide complete, clear
and tested solution.
Our application works with ftp/sftp in 10 parallel threads by default using
commons-vfs2 (versions 2.4, 2.6.0) for at least 2-3 years on many environments,
and we haven't had such problems until update to 2.9.0.
Thank You.
> DeadLock on SftpFileObject
> --------------------------
>
> Key: VFS-817
> URL: https://issues.apache.org/jira/browse/VFS-817
> Project: Commons VFS
> Issue Type: Bug
> Affects Versions: 2.9.0
> Reporter: Mykhailo
> Priority: Major
> Attachments: cores.zip
>
>
> Deadlock happens on SftpFileObject.
> {color:#000000}No matter using shared between threads
> StandardFileSystemManager or separate manager for each thread (different
> stack trace in core, but still deadlock){color}
> Not reproduced on 2.8.0.
> Core files in attach (one for separate
> {color:#000000}StandardFileSystemManager {color}, one for shared between
> threads)
>
>
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
