Skip to content

[MDEPLOY-214] retryFailedDeploymentCount=10 retries and fails immediately without a waiting time between retries #372

Description

@jira-importer

Pablo Alcaraz opened MDEPLOY-214 and commented

a pom.xml file with:

<plugin>
    <groupId>org.apache.maven.plugins</groupId>
    <artifactId>maven-deploy-plugin</artifactId>
    <version>2.8.2</version>
    <configuration>
        <retryFailedDeploymentCount>10</retryFailedDeploymentCount>
    </configuration>
</plugin>
[INFO] Uploading: http://mvnrepository:8080/repository/ailive-central/com/mycompany/frontend-async/0.1.0-SNAPSHOT/frontend-async-0.1.0-20160927.211519-46-allinone.jar
Sep 27, 2016 2:15:22 PM org.apache.maven.wagon.providers.http.httpclient.impl.execchain.RetryExec execute
INFO: I/O exception (java.net.SocketException) caught when processing request to {}->http://mvnrepository:8080: Connection reset
Sep 27, 2016 2:15:22 PM org.apache.maven.wagon.providers.http.httpclient.impl.execchain.RetryExec execute
INFO: Retrying request to {}->http://mvnrepository:8080
[WARNING] Encountered issue during deployment: Failed to deploy artifacts: Could not transfer artifact com.mycompany:frontend-async:jar:allinone:0.1.0-20160927.211519-46 from/to ailive-central (http://mvnrepository:8080/repository/ailive-central): Connect to mvnrepository:8080 [mvnrepository/172.17.0.180] failed: Connection refused
[INFO] Retrying deployment attempt 2 of 10
[INFO] Uploading: http://mvnrepository:8080/repository/ailive-central/com/mycompany/frontend-async/0.1.0-SNAPSHOT/frontend-async-0.1.0-20160927.211519-46-allinone.jar
[WARNING] Encountered issue during deployment: Failed to deploy artifacts: Could not transfer artifact com.mycompany:frontend-async:jar:allinone:0.1.0-20160927.211519-46 from/to ailive-central (http://mvnrepository:8080/repository/ailive-central): Connect to mvnrepository:8080 [mvnrepository/172.17.0.180] failed: Connection refused
[INFO] Retrying deployment attempt 3 of 10
[INFO] Uploading: http://mvnrepository:8080/repository/ailive-central/com/mycompany/frontend-async/0.1.0-SNAPSHOT/frontend-async-0.1.0-20160927.211519-46-allinone.jar
[WARNING] Encountered issue during deployment: Failed to deploy artifacts: Could not transfer artifact com.mycompany:frontend-async:jar:allinone:0.1.0-20160927.211519-46 from/to ailive-central (http://mvnrepository:8080/repository/ailive-central): Connect to mvnrepository:8080 [mvnrepository/172.17.0.180] failed: Connection refused
[INFO] Retrying deployment attempt 4 of 10
[INFO] Uploading: http://mvnrepository:8080/repository/ailive-central/com/mycompany/frontend-async/0.1.0-SNAPSHOT/frontend-async-0.1.0-20160927.211519-46-allinone.jar
[WARNING] Encountered issue during deployment: Failed to deploy artifacts: Could not transfer artifact com.mycompany:frontend-async:jar:allinone:0.1.0-20160927.211519-46 from/to ailive-central (http://mvnrepository:8080/repository/ailive-central): Connect to mvnrepository:8080 [mvnrepository/172.17.0.180] failed: Connection refused
[INFO] Retrying deployment attempt 5 of 10
[INFO] Uploading: http://mvnrepository:8080/repository/ailive-central/com/mycompany/frontend-async/0.1.0-SNAPSHOT/frontend-async-0.1.0-20160927.211519-46-allinone.jar
[WARNING] Encountered issue during deployment: Failed to deploy artifacts: Could not transfer artifact com.mycompany:frontend-async:jar:allinone:0.1.0-20160927.211519-46 from/to ailive-central (http://mvnrepository:8080/repository/ailive-central): Connect to mvnrepository:8080 [mvnrepository/172.17.0.180] failed: Connection refused
[INFO] Retrying deployment attempt 6 of 10
[INFO] Uploading: http://mvnrepository:8080/repository/ailive-central/com/mycompany/frontend-async/0.1.0-SNAPSHOT/frontend-async-0.1.0-20160927.211519-46-allinone.jar
[WARNING] Encountered issue during deployment: Failed to deploy artifacts: Could not transfer artifact com.mycompany:frontend-async:jar:allinone:0.1.0-20160927.211519-46 from/to ailive-central (http://mvnrepository:8080/repository/ailive-central): Connect to mvnrepository:8080 [mvnrepository/172.17.0.180] failed: Connection refused
[INFO] Retrying deployment attempt 7 of 10
[INFO] Uploading: http://mvnrepository:8080/repository/ailive-central/com/mycompany/frontend-async/0.1.0-SNAPSHOT/frontend-async-0.1.0-20160927.211519-46-allinone.jar
[WARNING] Encountered issue during deployment: Failed to deploy artifacts: Could not transfer artifact com.mycompany:frontend-async:jar:allinone:0.1.0-20160927.211519-46 from/to ailive-central (http://mvnrepository:8080/repository/ailive-central): Connect to mvnrepository:8080 [mvnrepository/172.17.0.180] failed: Connection refused
[INFO] Retrying deployment attempt 8 of 10
[INFO] Uploading: http://mvnrepository:8080/repository/ailive-central/com/mycompany/frontend-async/0.1.0-SNAPSHOT/frontend-async-0.1.0-20160927.211519-46-allinone.jar
[WARNING] Encountered issue during deployment: Failed to deploy artifacts: Could not transfer artifact com.mycompany:frontend-async:jar:allinone:0.1.0-20160927.211519-46 from/to ailive-central (http://mvnrepository:8080/repository/ailive-central): Connect to mvnrepository:8080 [mvnrepository/172.17.0.180] failed: Connection refused
[INFO] Retrying deployment attempt 9 of 10
[INFO] Uploading: http://mvnrepository:8080/repository/ailive-central/com/mycompany/frontend-async/0.1.0-SNAPSHOT/frontend-async-0.1.0-20160927.211519-46-allinone.jar
[WARNING] Encountered issue during deployment: Failed to deploy artifacts: Could not transfer artifact com.mycompany:frontend-async:jar:allinone:0.1.0-20160927.211519-46 from/to ailive-central (http://mvnrepository:8080/repository/ailive-central): Connect to mvnrepository:8080 [mvnrepository/172.17.0.180] failed: Connection refused
[INFO] Retrying deployment attempt 10 of 10
[INFO] Uploading: http://mvnrepository:8080/repository/ailive-central/com/mycompany/frontend-async/0.1.0-SNAPSHOT/frontend-async-0.1.0-20160927.211519-46-allinone.jar

Affects: 2.8.2

Issue Links:

  • WAGON-575 Retry for connection issues
    ("duplicates")

Remote Links:

1 votes, 5 watchers

Activity

  1. jira-importer commented on Sep 28, 2016

    @jira-importer
    Author
  2. jira-importer commented on Nov 3, 2016

    @jira-importer
    Author

    Michael Osipov commented

    If your Nexus instance fails ten times in a row, you should really seek out the admin. Such an improvements is helpful on unreliable links but not for buggy servers.

  3. jira-importer commented on Nov 3, 2016

    @jira-importer
    Author

    Pablo Alcaraz commented

    It is not an admin thing. We have around 100+ maven repositories in that archiva instance. They are created and deleted several time at day. Sometimes when a number of maven repositories are deleted, the archiva instance decides to do some housekeeping (I ignore what it is specifically doing) and archiva server stops processing http requests for 30 or 40 seconds until it is done.

    Besides, if the plugin is configured to retry 10 times, then it retries the 10 times in less than a second. I understand that is not the idea of the retry policy.

    I believe there is a valid user scenario for this setting.

  4. jira-importer commented on Nov 3, 2016

    @jira-importer
    Author

    Michael Osipov commented

    Thanks for the explanation. Makes sense, still weird about Archiva because it could block only a fraction of the system whithout impairing the rest of the users. Waiting for the seperate MSHARED issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't workingpriority:majorMajor loss of function

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions