[Commented] (MRESOLVER-123) Concurrency issues

classic Classic list List threaded Threaded
1 message Options
Reply | Threaded
Open this post in threaded view

[Commented] (MRESOLVER-123) Concurrency issues

Piotr Zygielo (Jira)

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

Rainer Reich commented on MRESOLVER-123:

Do we need to update our Nexus 2 instances to 2.14.18 (we are on 2.14.17 currently) to be compatible with the next maven(-resolver) release?
Or do you think our Nexus is somehow broken / configured in a wrong way?
And what exactly do you mean with 'log with headers only'?

> 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
>            Priority: Critical
>         Attachments: checksum-error-debug.log
> 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