[
https://issues.apache.org/jira/browse/WAGON-545?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16753902#comment-16753902
]
Oleg Kalnichevski commented on WAGON-545:
-----------------------------------------
{quote}why do we have connection resets on Maven Central? It is either the
outboud connection with the NAT on Azure or the inbound reverse proxy of Maven
Central has a 5 min cap without a proper keep-alive header{quote}
[~michael-o] Connections resets can happen for all sorts of reasons,
connections dropped due to inactivity being just one. Ideally the HTTP
transport code should be resilient enough to recover from such I/O failures. In
case of HttpWagon that uses HTTP GET to download artifacts re-executing
requests failed due to {{SocketException}} should be the simplest and most
reasonable thing to do.
Oleg
> Connection reset while downloading artefacts in cloud environment (Azure)
> -------------------------------------------------------------------------
>
> Key: WAGON-545
> URL: https://issues.apache.org/jira/browse/WAGON-545
> Project: Maven Wagon
> Issue Type: Bug
> Components: wagon-http
> Affects Versions: 3.2.0
> Environment: Microsoft Azure 'Hosted VS2017'
> Reporter: Christian Domsch
> Priority: Major
> Fix For: waiting-for-feedback
>
> Attachments: log_10_310.zip, log_10_311.zip, log_10_325.zip
>
>
> We are building a huge multi-module project in the azure cloud and experience
> random connection resets during our build due to probably the same issue as
> in WAGON-486. Since it is stated by Microsoft that they terminate connections
> that are idle for longer than four minutes (see solution comment
> [here|https://developercommunity.visualstudio.com/content/problem/357696/maven-project-build-failing-with-connection-reset.html],
> I set -Dmaven.wagon.httpconnectionManager.ttlSeconds=120. Also, disabling
> the http pool does not solve the problem. Attached are logs from out main
> build with logging turned on for the wagon components, as mentioned in the
> comment section of WAGON-486.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
