Mailing-List: contact issues-help@maven.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@maven.apache.org
Date: Mon, 29 May 2017 08:32:04 +0000 (UTC)
From: "Michael Osipov (JIRA)" <jira@apache.org>
To: issues@maven.apache.org
Message-ID: <JIRA.13034573.1484302234000.313731.1496046724210@Atlassian.JIRA>
In-Reply-To: <JIRA.13034573.1484302234000@Atlassian.JIRA>
References: <JIRA.13034573.1484302234000@Atlassian.JIRA> <JIRA.13034573.1484302234082@jira-lw-us.apache.org>
Subject: [jira] [Commented] (MRESOLVER-25) Resume support is broken under
 high concurrency
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Mon, 29 May 2017 08:32:08 -0000


    [ https://issues.apache.org/jira/browse/MRESOLVER-25?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16028140#comment-16028140 ] 

Michael Osipov commented on MRESOLVER-25:
-----------------------------------------

Did you receive the exception even with the resume support disabled?

> Resume support is broken under high concurrency
> -----------------------------------------------
>
>                 Key: MRESOLVER-25
>                 URL: https://issues.apache.org/jira/browse/MRESOLVER-25
>             Project: Maven Resolver
>          Issue Type: Bug
>          Components: resolver
>    Affects Versions: Maven Artifact Resolver 1.0.3
>            Reporter: Roland Illig
>         Attachments: dependency-list.txt, dependency-list-x.zip, wagon-not-threadsafe.zip
>
>
> When building a multi-module project in parallel, Maven updates the local Maven repository without taking into account that other threads or processes might do the same at the same time.
> To reproduce:
> 1.  unpack the attached project
> 2.  {{mvn dependency:list -U -B -T100}}
> See the attached {{dependency-list.txt}} for an example output.
> First thing to notice is that the dependency is downloaded 100 times. This is unexpected, since the Reactor should coordinate all the modules.
> Second thing to notice is that the build fails, since a dependency "cannot be found". This is wrong, since the dependency _can_ be found, it's just not processed properly.
> I suspect the {{legacy.DefaultWagonManager}} to be the cause of this, since the typical error messages are:
> * {{"Downloaded file does not exist: "}}
> * {{"Error copying temporary file to the final destination: "}}
> * {{"*** CHECKSUM FAILED - RETRYING"}}


--
This message was sent by Atlassian JIRA
(v6.3.15#6346)