[ https://issues.apache.org/jira/browse/MRESOLVER-123?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17150986#comment-17150986 ]
Philippe GRANET commented on MRESOLVER-123: ------------------------------------------- I found these two maven extensions that try to fix concurrency problem: * [https://github.com/evanchsa/maven-parallel-resolver] 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=...) * [https://github.com/murkaje/robust-maven-cache] Not tested > 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, 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 (v8.3.4#803005)