maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Philippe GRANET (Jira)" <>
Subject [jira] [Commented] (MRESOLVER-123) Concurrency issues
Date Fri, 03 Jul 2020 13:11:00 GMT


Philippe GRANET commented on MRESOLVER-123:

I found these two maven extensions that try to fix concurrency problem:
 * []

It works in one JVM, it synchronizes the whole resolve-Method, but it has performance impact
since all downloads are sequential, it disable maven parallel download (mvn -T ... and also
mvn -Dmaven.artifact.threads=...)
 * []

Not tested

> Concurrency issues
> ------------------
>                 Key: MRESOLVER-123
>                 URL:
>             Project: Maven Resolver
>          Issue Type: Bug
>          Components: resolver
>    Affects Versions: 1.4.2
>            Reporter: Michael Osipov
>            Priority: Critical
>         Attachments: checksum-error-debug.log, successful-sha1-log.txt
> 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

View raw message