You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@maven.apache.org by "Michael Osipov (Jira)" <ji...@apache.org> on 2021/08/28 22:45:00 UTC

[jira] [Closed] (MRESOLVER-190) [Regression] Revert MRESOLVER-184

     [ https://issues.apache.org/jira/browse/MRESOLVER-190?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Michael Osipov closed MRESOLVER-190.
------------------------------------
    Resolution: Fixed

Fixed with [e8fb972b1e6bed5c0873a9f9277a5ceff50f8d5c|https://gitbox.apache.org/repos/asf?p=maven-resolver.git;a=commit;h=e8fb972b1e6bed5c0873a9f9277a5ceff50f8d5c].

> [Regression] Revert MRESOLVER-184
> ---------------------------------
>
>                 Key: MRESOLVER-190
>                 URL: https://issues.apache.org/jira/browse/MRESOLVER-190
>             Project: Maven Resolver
>          Issue Type: Task
>          Components: Resolver
>    Affects Versions: 1.7.1
>            Reporter: Michael Osipov
>            Assignee: Michael Osipov
>            Priority: Major
>             Fix For: 1.7.2
>
>
> As it turns out the deletion of the semaphore results in a race condition when multiple Maven instances are trying to use the semaphore. The result is they lock up until the timeout is reached and the build fails. See also: https://github.com/redisson/redisson/issues/3728



--
This message was sent by Atlassian Jira
(v8.3.4#803005)