[jira] [Comment Edited] (WAGON-545) Connection reset while downloading artefacts in cloud environment (Azure)

["Christian Domsch (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/WAGON-545?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16749926#comment-16749926 ] 

Christian Domsch edited comment on WAGON-545 at 1/23/19 12:58 PM:
------------------------------------------------------------------

Ok, changed to maven 3.6.0, got rid of the extensions and have finally a good log. This is the commandline that maven was started with (is also visible inside the log btw):

{noformat}
mvn -B -U -s settings.xml -Dmaven.wagon.httpconnectionManager.ttlSeconds=120 -Dorg.slf4j.simpleLogger.log.org.apache.maven.wagon.providers.http.httpclient=DEBUG -Dorg.slf4j.simpleLogger.log.org.apache.maven.wagon.providers.http.httpclient.wire=ERROR -Dorg.slf4j.simpleLogger.log.org.apache.maven.wagon.providers.http.httpclient.impl.conn=DEBUG -Dorg.slf4j.simpleLogger.log.org.apache.maven.wagon.providers.http.httpclient.impl.client=DEBUG -Dorg.slf4j.simpleLogger.log.org.apache.maven.wagon.providers.http.httpclient.client=DEBUG install
{noformat}

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.


was (Author: cdomsch):
Ok, changed to maven 3.6.0, got rid of the extensions and have finally a good log. This is the commandline that maven was started with (is also visible inside the log btw):

{noformat}
-B -U -s settings.xml -Dmaven.wagon.httpconnectionManager.ttlSeconds=120 -Dorg.slf4j.simpleLogger.log.org.apache.maven.wagon.providers.http.httpclient=DEBUG -Dorg.slf4j.simpleLogger.log.org.apache.maven.wagon.providers.http.httpclient.wire=ERROR -Dorg.slf4j.simpleLogger.log.org.apache.maven.wagon.providers.http.httpclient.impl.conn=DEBUG -Dorg.slf4j.simpleLogger.log.org.apache.maven.wagon.providers.http.httpclient.impl.client=DEBUG -Dorg.slf4j.simpleLogger.log.org.apache.maven.wagon.providers.http.httpclient.client=DEBUG
{noformat}

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.

> 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=180. 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)