Uploaded image for project: 'Maven Wagon'
  1. Maven Wagon
  2. WAGON-567

Provide request retry strategy on transient client and server side errors

    XMLWordPrintableJSON

    Details

    • Type: New Feature
    • Status: Closed
    • Priority: Minor
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 3.3.4
    • Component/s: wagon-http
    • Labels:
      None

      Description

      Currently wagon has a retry mechanism when there are connections issues with repository manager like maven central, artifactory or nexus, see wagon source and httpclient source, httpclient default retry handler. However,  it only captures low level connection issues. When the repo returns errors like 500 or 503, it does not retry. The 5xx response from the repo might be a blip and maven should retry before giving up.

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                michael-o Michael Osipov
                Reporter:
                ChandlerZhang xueqian zhang
              • Votes:
                0 Vote for this issue
                Watchers:
                3 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved:

                  Time Tracking

                  Estimated:
                  Original Estimate - Not Specified
                  Not Specified
                  Remaining:
                  Remaining Estimate - 0h
                  0h
                  Logged:
                  Time Spent - 20m
                  20m