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

Oleg Kalnichevski commented on WAGON-545:
-----------------------------------------

[~michael-o]: 

{quote}What baffles me is that between the last get and the closure there is a 
20 second gap and no response{quote}
That is probably OK. The client was trying to send packets to the opposite 
endpoint and was blocked in the write operation until the connection get 
{{RST}}-ed. Please note that in the blocking i/o the socket timeout apples to 
read operations only. 

{quote}The connection should have been invalidated and not reused.{quote}
Yes, it clearly should have been discarded and never re-used. This looks 
troubling. 

What version of HttpClient is being used by the Maven Wagon in this particular 
case? Is there any chance it could be upgraded to 4.5.7?

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
>
>
> 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)

Reply via email to