[
https://issues.apache.org/jira/browse/WAGON-486?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16489113#comment-16489113
]
Victor commented on WAGON-486:
------------------------------
[~michael-o], first, sorry, I didn't read everything here before posting my
comment, now I have :)
I better understand your point of view. My comment was actually directed at the
fact that after the connection did time out inside the java process (the
SocketException in the logs in my comment), the situation does not seem
resolved for the next one, but I suppose this is because another problematic
connection in the pool was reused instead of a new one created, so I understand
why it doesn't solve the problem.
If I understand correctly, along trying your patch, I should see if I can
change the NAT settings of my VM (it's managed by Azure) or complain to the
provider about this situation that does not respect HTTP?
As for the patch, if I understand correctly, it limits the time a connection is
kept so that it is thrown away fast enough (in less time than the NAT timeout)
for it not to be in this unusable state we encounter, right?
I suppose the best solution to this situation would be for the pooled
connections to be kept actively alive by sending stuffs over them so that they
are never considered idle by the NAT…
I will see if I can test the patch, I don't guarantee it though.
> 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)
