[
https://issues.apache.org/jira/browse/VFS-817?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17507815#comment-17507815
]
Gary D. Gregory commented on VFS-817:
-------------------------------------
Hi [~Mykhailoz]
Thank you for your report.
I am leary of this type of change ATM, especially without a PR on GitHub with a
test proving it solves anything. The simplest solution is for the app to
serialize access to VFS objects. One issue in VFS is that each provider does
not mostly make claims regarding thread safety, single-thread access is usually
assumed and it only in the fairly recent past that we've made any attempts to
help multi-threaded apps here and there. It also doubtful that changing just
this one method will be enough even if your empirical evidence shows your
current issue possibly resovled.
So step one for any progress would be to provide a PR on GitHub.
TY!
> 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)
