[ https://issues.apache.org/jira/browse/MRESOLVER-123?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17150914#comment-17150914 ]
Eva Müller commented on MRESOLVER-123: -------------------------------------- Hi [~michael-o], great to see the progress this topic made. As [~rreich] wrote, the 1000 builds are the sum of the last month, but if we use a patched Maven internally, we should be able to produce some results again. I have two additional questions: 1. You wrote bq. I have tried 2.14.16 too at work. [...] You may have trouble if you use Nexus Pro with staging rules as done by repository.apache.org. What problem will occur? We use a Nexus Pro {{Nexus Repository Manager 2.14.17-01}} including the staging feature. 2. What is the expected release date for 3.7.0? > 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)