Mailing-List: contact issues-help@maven.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@maven.apache.org
Date: Fri, 22 Dec 2017 16:14:00 +0000 (UTC)
From: "Robert Scholte (JIRA)" <jira@apache.org>
To: issues@maven.apache.org
Message-ID: <JIRA.13125692.1513624709000.520436.1513959240083@Atlassian.JIRA>
In-Reply-To: <JIRA.13125692.1513624709000@Atlassian.JIRA>
References: <JIRA.13125692.1513624709000@Atlassian.JIRA> <JIRA.13125692.1513624709965@jira-lw-us.apache.org>
Subject: [jira] [Commented] (MNG-6323) Deadlock in multithreaded dependency
 resolution
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Fri, 22 Dec 2017 16:14:05 -0000


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

Robert Scholte commented on MNG-6323:
-------------------------------------

So one of the following changes seems to have more impact than expected: https://issues.apache.org/jira/projects/MRESOLVER/versions/12339212

> Deadlock in multithreaded dependency resolution
> -----------------------------------------------
>
>                 Key: MNG-6323
>                 URL: https://issues.apache.org/jira/browse/MNG-6323
>             Project: Maven
>          Issue Type: Bug
>    Affects Versions: 3.5.2
>            Reporter: Ben Caradoc-Davies
>         Attachments: geoserver-community-maven-hang-jstack-2.txt, geoserver-community-maven-hang-jstack.txt
>
>
> Maven 3.5.2 multithreaded builds experience a deadlock not seen with Maven 3.5.0.
> To reproduce the issue, clone GeoServer:
> {noformat}
> git clone https://github.com/geoserver/geoserver.git
> cd geoserver
> {noformat}
> Build GeoServer community modules with:
> {noformat}
> mvn -f src/community/pom.xml -B -T4 -U -Prelease -PcommunityRelease -DskipTests clean install
> {noformat}
> Builds that normally take 2-4 minutes instead experience long hangs. {{jstack}} output (attached) suggests a deadlock (two different hangs attached). Some of the locks are in {{TIME_WAIT}} and eventually the build completes after 30-45 minutes, but this is enough to cause builds on Travis to be killed for their failure to output for ten minutes. (Travis upgraded to Maven 3.5.2 a week ago.)
> I have only seen the failures with -U. The hang does not occur in single-threaded builds. There are no "*.lock" files in the local repository during the hang so the deadlocks are not mediated by the filesystem. CPU utilisation is zero suggesting a deadlock not a livelock.
> See also discussion on the geoserver-devel mailing list: http://osgeo-org.1560.x6.nabble.com/Travis-failures-started-with-new-trusty-images-td5346836.html


--
This message was sent by Atlassian JIRA
(v6.4.14#64029)