[
https://issues.apache.org/jira/browse/WAGON-545?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16749962#comment-16749962
]
Michael Osipov commented on WAGON-545:
--------------------------------------
bq. Possible interesting information for you, Michael: the reason why the debug
logs stopped once the reactor started in the previous run is due to the fact
that I used the extension mechanism to pull in wagon 3.3.1. So, this tampers
somehow with the logging information. Not sure if this useful information for
you.
This pretty much explains why the log was shut off. Maven uses
{{wagon-htttp-shaded}}. HttpClient has different package names, that's why the
logging went away.
> 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.3.1
> Environment: Microsoft Azure 'Hosted VS2017'
> Reporter: Christian Domsch
> Priority: Major
> Fix For: waiting-for-feedback
>
> Attachments: log_10_310.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)
