[
https://issues.apache.org/jira/browse/WAGON-545?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16753175#comment-16753175
]
Michael Osipov commented on WAGON-545:
--------------------------------------
[~olegk], please have a look at connection 273. By stale in terms of TTL set up
by us. There is a 6 min gap between next to last and last use. The connection
should have been invalidated and not reused:
{noformat}
2019-01-23T14:51:53.4428569Z
[BasicRepositoryConnector-repo.maven.apache.org-126-4] [DEBUG] Connection
leased: [id: 273][route: {s}->https://repo.maven.apache.org:443][total kept
alive: 2; route allocated: 5 of 20; total allocated: 5 of 40]
{noformat}
and
{noformat}
2019-01-23T14:57:41.0140402Z
[BasicRepositoryConnector-repo.maven.apache.org-136-0] [DEBUG] Connection
leased: [id: 273][route: {s}->https://repo.maven.apache.org:443][total kept
alive: 2; route allocated: 5 of 20; total allocated: 5 of 40]
{noformat}
I would have expected that this connection should have invalidated by now.
> 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)
