Details
-
Bug
-
Status: Closed
-
Major
-
Resolution: Fixed
-
3.1.0
-
None
Description
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
Attachments
Attachments
Issue Links
- depends upon
-
WAGON-531 Add default TTL for HTTP connections
- Closed
- links to