[
https://issues.apache.org/jira/browse/MNG-6199?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15948630#comment-15948630
]
Martin Myslík commented on MNG-6199:
------------------------------------
It is happening on Atlassian Pipelines
(https://confluence.atlassian.com/bitbucket/bitbucket-pipelines-792496469.html).
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: https://issues.apache.org/jira/browse/MNG-6199
> 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):
> https://bitbucket.org/site/master/issues/13988/pipelines-kills-idle-maven-connections
> 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 issue.
> Thank you for your input.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
