[
https://issues.apache.org/jira/browse/WAGON-486?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16488927#comment-16488927
]
Michael Osipov commented on WAGON-486:
--------------------------------------
bq. So I don't understand why the pool does not simply close a connection that
times out… ?!
How is the pool supposed to know that if the server or intermediate does not
tell? I have added a lot of explations about the given behavior.
[~victor.noel], can you verify that the inline patch works for you?
What we can do is to set a default timeout of 5 minutes, make this configurable
and even with -1 to have indefitive lifetime.
> Wagon fails to download artifacts if number of dropped pooled connections (by
> intermediate) are greater than default retry count
> --------------------------------------------------------------------------------------------------------------------------------
>
> Key: WAGON-486
> URL: https://issues.apache.org/jira/browse/WAGON-486
> Project: Maven Wagon
> Issue Type: Bug
> Reporter: Martin Myslík
> Priority: Major
> Attachments: build-failure-maven-3.5.0-patched-debug-updated.txt,
> build-failure-maven-3.5.0-patched-debug.txt, build-failure-vanilla.txt,
> build-success-keep-alive-false.txt,
> build-success-maven-3.5.0-patched-debug.txt, build-success-pooling-false.txt,
> dump-failed-build.pcap, dump.pcap
>
>
> 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
(v7.6.3#76005)
