[
https://issues.apache.org/jira/browse/MNG-6199?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15954066#comment-15954066
]
Michael Osipov edited comment on MNG-6199 at 4/3/17 8:04 PM:
-------------------------------------------------------------
I think that Atlassian won't do anything becuase of hard AWS configuration.
Quoting from [here|http://tldp.org/HOWTO/TCP-Keepalive-HOWTO/overview.html]:
bq. The other useful goal of keepalive is to prevent inactivity from
disconnecting the channel. It's a very common issue, when you are behind a NAT
proxy or a firewall, to be disconnected without a reason. This behavior is
caused by the connection tracking procedures implemented in proxies and
firewalls, which keep track of all connections that pass through them. Because
of the physical limits of these machines, they can only keep a finite number of
connections in their memory. The most common and logical policy is to keep
newest connections and to discard old and inactive connections first.
Same is written on Wikipedia. ...wating for your logs.
I am also afraid that {{SO_KEEPALIVE}} won't help, read
[here|https://docs.oracle.com/javase/6/docs/api/java/net/SocketOptions.html#SO_KEEPALIVE]
and
[here|http://coryklein.com/tcp/2015/11/25/custom-configuration-of-tcp-socket-keep-alive-timeouts.html].
was (Author: michael-o):
I think that Atlassian won't do anything becuase of hard AWS configuration.
Quoting from [here|http://tldp.org/HOWTO/TCP-Keepalive-HOWTO/overview.html]:
bq. The other useful goal of keepalive is to prevent inactivity from
disconnecting the channel. It's a very common issue, when you are behind a NAT
proxy or a firewall, to be disconnected without a reason. This behavior is
caused by the connection tracking procedures implemented in proxies and
firewalls, which keep track of all connections that pass through them. Because
of the physical limits of these machines, they can only keep a finite number of
connections in their memory. The most common and logical policy is to keep
newest connections and to discard old and inactive connections first.
Same is written on Wikipedia. ...wating for your logs.
I am also afraid that {{SO_KEEPALIVE}} won't help, read
[here|https://docs.oracle.com/javase/6/docs/api/java/net/SocketOptions.html#SO_KEEPALIVE].
> 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-vanilla.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)
