[
https://issues.apache.org/jira/browse/WAGON-486?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16491793#comment-16491793
]
Michael Osipov commented on WAGON-486:
--------------------------------------
bq. Michael Osipov, ok, I can do that, how should I proceed? I have no idea
how to use tcpdump. I just run it in parallel to the maven execution and wait
for the problem to appear? I suppose it would be best if done with maven 3.5.3,
right?
Just install Wireshark on your machine, start capturing and let Maven work. As
soon as you see the error, have Maven finish the build and stop Wireshark. Save
it to a GZipped pcap file and upload it.
bq. oncerning the keep-alive, this means that a workaround is to reduce the
value of keep alive (from 2hours to say 1mn) on the machine?
You can do that on the OS level, yes. In fact, Java uses the default of 2 h
which is way too long. I read the net-dev@openjdk mailing list yesterday there
are efforts to make {{SO_KEEPALIVE}} available from within Java.
> 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)
