You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Karl Heinz Marbaise (JIRA)" <ji...@apache.org> on 2017/03/30 08:07:41 UTC
[jira] [Commented] (MNG-6199) Maven does not attempt to reconnect
reset connections
[ https://issues.apache.org/jira/browse/MNG-6199?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15948615#comment-15948615 ]
Karl Heinz Marbaise commented on MNG-6199:
------------------------------------------
Is this happening on an open source project? Cause you are using Maven central directly ?
> 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)