[
https://issues.apache.org/jira/browse/MRESOLVER-123?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17148691#comment-17148691
]
Michael Osipov commented on MRESOLVER-123:
------------------------------------------
bq. 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?
I have tried 2.14.16 too at work. It looked weird while browsing, but did work.
I would recommend testing anyway.
bq. Or do you think our Nexus is somehow broken / configured in a wrong way?
I think so, because Nexus < 2.14.18 will not produce SHA-2 hashes. You may
purge Nexus storage for Central and retry.
Headers only means
{{org.slf4j.simpleLogger.log.org.apache.maven.wagon.providers.http.httpclient.wire=off}},
but leave the rest.
> 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)
