maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Martin Myslík (JIRA) <>
Subject [jira] [Commented] (MNG-6199) Maven does not attempt to reconnect reset connections
Date Thu, 30 Mar 2017 08:15:41 GMT


Martin Myslík commented on MNG-6199:

It is happening on Atlassian Pipelines (
But the issue is generally with AWS NAT configuration and Maven not being able to handle connections
that are killed by it.

I am basically running 'mvn install' which first donwloads all necessary dependencies, runs
tests for 15 mintues and then triggers an additional phase which needs more artifacts from
Maven central but the build fails because the connection has been killed in the meantime.
I am able to make it work by using 'mvn -Dmaven.wagon.http.pool=false clean install' but that
just seems like a dirty hack.

> Maven does not attempt to reconnect reset connections
> -----------------------------------------------------
>                 Key: MNG-6199
>                 URL:
>             Project: Maven
>          Issue Type: Bug
>            Reporter: Martin Myslík
> I was recently discussing and issue with Atlassian team concerning failing build on Atlassian
Pipelines when running Maven build for more than 5 minutes.
> The issue was with NAT timeout which kills all idle connections after 5 mintues and Maven
does not try to reconnect once the connection is killed (and hence cannot download artifacts
from Maven central).
> Please, take a look at the open issue (it contains more detailed description and also
comments from Atlassian which suggested opening an issue with Maven):
> Could you, please, take a minute and explain how could proceed with solving this issue?
I am not sure whether this is something that Maven should handle or whether it is Atlassians
> Thank you for your input. 

This message was sent by Atlassian JIRA

View raw message