XMLWordPrintable

    Details

    • Type: Bug
    • Status: Resolved
    • Priority: Critical
    • Resolution: Fixed
    • Affects Version/s: NXP-9.x, NXP-10.x
    • Fix Version/s: NXP-9.x, NXP-10.x
    • Component/s: HotFix factory

      Description

      The move from one repository to another (or a delete operation) ends up with 504.

      For example:

      23:24:01  com.sonatype.nexus.api.zz.fl: Gateway Time-out
      23:24:01  	at com.sonatype.nexus.api.zz.fm.handleResponse(SourceFile:51)
      23:24:01  	at org.apache.http.impl.client.CloseableHttpClient.execute(SourceFile:223)
      23:24:01  	at org.apache.http.impl.client.CloseableHttpClient.execute(SourceFile:165)
      23:24:01  	at com.sonatype.nexus.api.zz.fg.a(SourceFile:84)
      23:24:01  Caused: com.sonatype.nexus.api.exception.RepositoryManagerException: Move components was unsuccessful (504 response from server)
      23:24:01  	at com.sonatype.nexus.api.zz.fg.a(SourceFile:106)
      23:24:01  	at com.sonatype.nexus.api.zz.fg.a(SourceFile:87)
      23:24:01  	at com.sonatype.nexus.api.zz.ff.move(SourceFile:231)
      23:24:01  	at org.sonatype.nexus.ci.nxrm.v3.MoveComponentsStep.perform(MoveComponentsStep.java:126)
      23:24:01  Caused: java.io.IOException
      23:24:01  	at org.sonatype.nexus.ci.nxrm.v3.MoveComponentsStep.perform(MoveComponentsStep.java:133)
      23:24:01  	at org.jenkinsci.plugins.workflow.steps.CoreStep$Execution.run(CoreStep.java:80)
      23:24:01  	at org.jenkinsci.plugins.workflow.steps.CoreStep$Execution.run(CoreStep.java:67)
      23:24:01  	at org.jenkinsci.plugins.workflow.steps.SynchronousNonBlockingStepExecution.lambda$start$0(SynchronousNonBlockingStepExecution.java:47)
      23:24:01  	at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
      23:24:01  	at java.util.concurrent.FutureTask.run(FutureTask.java:266)
      23:24:01  	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
      23:24:01  	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
      23:24:01  	at java.lang.Thread.run(Thread.java:748)
      23:24:01  Finished: FAILURE
      

      This happens when the number of artifacts is high (like a Nuxeo release).
      Moving around 50 artifacts does not generate the same issue.

      Retrying fails:

      23:34:49  com.sonatype.nexus.api.zz.fl: Bad Request
      23:34:49  	at com.sonatype.nexus.api.zz.fm.handleResponse(SourceFile:51)
      23:34:49  	at org.apache.http.impl.client.CloseableHttpClient.execute(SourceFile:223)
      23:34:49  	at org.apache.http.impl.client.CloseableHttpClient.execute(SourceFile:165)
      23:34:49  	at com.sonatype.nexus.api.zz.fg.a(SourceFile:84)
      23:34:49  Caused: com.sonatype.nexus.api.exception.RepositoryManagerException: Move components was unsuccessful (400 response from server)
      23:34:49  	at com.sonatype.nexus.api.zz.fg.a(SourceFile:106)
      23:34:49  	at com.sonatype.nexus.api.zz.fg.a(SourceFile:87)
      23:34:49  	at com.sonatype.nexus.api.zz.ff.move(SourceFile:231)
      23:34:49  	at org.sonatype.nexus.ci.nxrm.v3.MoveComponentsStep.perform(MoveComponentsStep.java:126)
      23:34:49  Caused: java.io.IOException
      23:34:49  	at org.sonatype.nexus.ci.nxrm.v3.MoveComponentsStep.perform(MoveComponentsStep.java:133)
      23:34:49  	at org.jenkinsci.plugins.workflow.steps.CoreStep$Execution.run(CoreStep.java:80)
      23:34:49  	at org.jenkinsci.plugins.workflow.steps.CoreStep$Execution.run(CoreStep.java:67)
      23:34:49  	at org.jenkinsci.plugins.workflow.steps.SynchronousNonBlockingStepExecution.lambda$start$0(SynchronousNonBlockingStepExecution.java:47)
      23:34:49  	at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
      23:34:49  	at java.util.concurrent.FutureTask.run(FutureTask.java:266)
      23:34:49  	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
      23:34:49  	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
      23:34:49  	at java.lang.Thread.run(Thread.java:748)
      23:34:49  Finished: FAILURE

      This is because the staging feature finishes the move after the request has been issued. After retrying, there is nothing left to move ending up in a 400 error.

      The new timeout needs to be high just in case of latency or network performance decrease.

        Attachments

          Activity

            People

            • Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                PagerDuty

                Error rendering 'com.pagerduty.jira-server-plugin:PagerDuty'. Please contact your Jira administrators.