[ https://issues.apache.org/jira/browse/MRESOLVER-123?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17148526#comment-17148526 ]
Michael Osipov commented on MRESOLVER-123: ------------------------------------------ Just ran tests with SHA-2 family. For this, I have uploaded SHA-256 and SHA-512 for an internal project and then ran: {{~/apache-maven-3.7.0-SNAPSHOT/bin/mvn -B -Dmaven.repo.local=$PWD/repo -Drat.skip -Daether.checksums.algorithms=SHA-256,SHA-512}} While all artifacts failed with {{org.eclipse.aether.transfer.ChecksumFailureException: Checksum validation failed, no checksums available}}, but the internal ones perfectly validated. Please validate your Nexus instance. > 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 (v8.3.4#803005)