maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "xueqian zhang (Jira)" <j...@apache.org>
Subject [jira] [Updated] (WAGON-567) Wagon should retry download on server side errors
Date Thu, 10 Oct 2019 01:42:00 GMT

     [ https://issues.apache.org/jira/browse/WAGON-567?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

xueqian zhang updated WAGON-567:
--------------------------------
    Description: Currently wagon has a retry mechanism when there are connections issues with
repository manager like maven central, artifactory or nexus, see [wagon source|https://github.com/apache/maven-wagon/blob/dfd22586b6b934aa5a652ca32d57ed26067432fd/wagon-providers/wagon-http-shared/src/main/java/org/apache/maven/wagon/shared/http/AbstractHttpClientWagon.java#L393]
and [httpclient source|https://github.com/apache/httpcomponents-client/blob/4.5.x/httpclient/src/main/java/org/apache/http/impl/execchain/RetryExec.java#L90],
[httpclient default retry handler|https://github.com/apache/httpcomponents-client/blob/4.5.x/httpclient/src/main/java/org/apache/http/impl/client/DefaultHttpRequestRetryHandler.java#L154].
However, when the repo returns errors like 500 or 503, it does not. The 5xx response from
the repo might be a blip and maven should retry before giving up.  (was: Currently wagon has
a retry mechanism when there are connections issues with repository manager like maven central,
artifactory or nexus, see [wagon source|[https://github.com/apache/maven-wagon/blob/dfd22586b6b934aa5a652ca32d57ed26067432fd/wagon-providers/wagon-http-shared/src/main/java/org/apache/maven/wagon/shared/http/AbstractHttpClientWagon.java#L403]]
and [httpclient source|[https://github.com/apache/httpcomponents-client/blob/4.5.x/httpclient/src/main/java/org/apache/http/impl/execchain/RetryExec.java#L90]].
However, when the repo returns errors like 500 or 503, it does not. The 5xx response from
the repo might be a blip and maven should retry before giving up.)

> Wagon should retry download on server side errors
> -------------------------------------------------
>
>                 Key: WAGON-567
>                 URL: https://issues.apache.org/jira/browse/WAGON-567
>             Project: Maven Wagon
>          Issue Type: New Feature
>          Components: wagon-http
>            Reporter: xueqian zhang
>            Priority: Minor
>             Fix For: waiting-for-feedback
>
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> Currently wagon has a retry mechanism when there are connections issues with repository
manager like maven central, artifactory or nexus, see [wagon source|https://github.com/apache/maven-wagon/blob/dfd22586b6b934aa5a652ca32d57ed26067432fd/wagon-providers/wagon-http-shared/src/main/java/org/apache/maven/wagon/shared/http/AbstractHttpClientWagon.java#L393]
and [httpclient source|https://github.com/apache/httpcomponents-client/blob/4.5.x/httpclient/src/main/java/org/apache/http/impl/execchain/RetryExec.java#L90],
[httpclient default retry handler|https://github.com/apache/httpcomponents-client/blob/4.5.x/httpclient/src/main/java/org/apache/http/impl/client/DefaultHttpRequestRetryHandler.java#L154].
However, when the repo returns errors like 500 or 503, it does not. The 5xx response from
the repo might be a blip and maven should retry before giving up.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Mime
View raw message