[
https://issues.apache.org/jira/browse/MRESOLVER-123?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17148558#comment-17148558
]
Rainer Reich commented on MRESOLVER-123:
----------------------------------------
Sorry, used the properties in a wrong way. I updated the log:
[^checksum-error-debug.log]
{code}
*cat
/nexus/sonatype-work/nexus/storage/central/.nexus/attributes/org/apache/maven/maven-parent/31/maven-parent-31.pom*
{"storageItem-readable":"true","storageItem-expired":"false","storageItem-modified":"1517529336000","storageItem-repositoryId":"central","storageItem-lastRequested":"1593503019625","storageItem-storedLocally":"1527072575313","remote.sha1":"e773af8e851de63461222f3a26d37e4619431e03","request.address":"10.1.13.242","storageItem-writable":"true","digest.md5":"236ee4e050fb10734caac73935b2e1f4","storageItem-created":"1517529336000","request.user":"anonymous","storageItem-path":"/org/apache/maven/maven-parent/31/maven-parent-31.pom","storageItem-remoteUrl":"https://repo1.maven.org/maven2/org/apache/maven/maven-parent/31/maven-parent-31.pom","request.isConfidential":"true","storageItem-checkedRemotely":"1533293300127","storageItem-generation":"1431","proxyRepository-invalidationToken":"11720965689239119","digest.sha1":"e773af8e851de63461222f3a26d37e4619431e03"}
{code}
> 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)
