You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Michael Osipov (Jira)" <ji...@apache.org> on 2020/06/18 09:04:00 UTC
[jira] [Created] (MRESOLVER-123) Concurrency issues
Michael Osipov created MRESOLVER-123:
----------------------------------------
Summary: Concurrency issues
Key: MRESOLVER-123
URL: https://issues.apache.org/jira/browse/MRESOLVER-123
Project: Maven Resolver
Issue Type: Bug
Components: resolver
Affects Versions: 1.4.2
Reporter: Michael Osipov
This is an umbrella ticket for a long standing issue with Maven Resolver: Our concurrency support is mediocre in a way that if two or more threads try to download the same file and fail to queue those write actions nicely. The problem is that The {{SyncContext}} and the its factory provided by Maven Resolver does not employ any locking at all. As layed out in detail in MRESOLVER-114 we need striped read write locks on artifacts and its metadata. This issue shall track progress on it. Even Takari Concurrent Repository extension does not help because it is only intended to synchronize concurrent access by multple JVMs and not threads.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)