[
https://issues.apache.org/jira/browse/WAGON-545?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov closed WAGON-545.
--------------------------------
Resolution: Fixed
Fixed implicitly by Fixed with
[dfd22586b6b934aa5a652ca32d57ed26067432fd|[https://gitbox.apache.org/repos/asf?p=maven-wagon.git;a=commit;h=dfd22586b6b934aa5a652ca32d57ed26067432fd].]
Azure users shall set the TTL to 240 seconds or less.
> Connection reset while downloading artifacts 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
> Assignee: Michael Osipov
> Priority: Major
> Fix For: 3.3.2
>
> Attachments: log_10_310.zip, log_10_311.zip, log_10_325.zip,
> successful-build-ttl5.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)
