[
https://issues.apache.org/jira/browse/MNG-6199?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15954933#comment-15954933
]
Michael Osipov commented on MNG-6199:
-------------------------------------
It defintively is. The log config I have provided for SLF4J Simple does work.
Did you mimic it for Log4J2?
> 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
> Attachments: build-failure-maven-3.5.0-patched-debug.txt,
> build-failure-maven-3.5.0-patched.txt, build-failure-vanilla.txt,
> build-maven-3.5.0.txt, build-success-keep-alive-false.txt,
> build-success-pooling-false.txt
>
>
> 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 is the link to my public repo with test project running tests for 15
> mintues. This build fails on Pipelines because of Maven connection that is
> being killed during the test: https://bitbucket.org/Smedzlatko/del-me
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
