Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-40507

maven plugin : build hang when downloading some artifacts

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Major Major
    • maven-plugin
    • None
    • jenkins 2.35
      master on rhel7.3
      slaves on rhel6.4
      using mvn 3.0.3
      maven plugin 2.14

      I have a build that downloads lots of poms and other artifacts from a nexus sitting on the same server as jenkins master.
      Next to this, I have a slave (next = in the same room).
      This all said to avoid 'network issues' explanations.

      The build runs ... then hangs randomly when trying to download something.

      [DEBUG] Using connector WagonRepositoryConnector with priority 0 for http://my-own-tihng/nexus/content/groups/public/
      Downloading: http://my-own-thing/nexus/content/groups/public/thing/ui/swing/gim-swing-texteditor/v3.1.23/gim-swing-texteditor-v3.1.23.pom
      

      it stops there,
      if I analyse the network queries : nothing.
      A memory dump of java process shows that a thread is waiting.... but didn't evn start to try to do anything.

      Note a fun thing :

      • this does happen when slave is connected over SSH
      • using a JNLP connection did apparently work around the issue (but it causes me other issues not to be exposed here)
      • running the maven command manually on the slave always works
      • I'd bet using a 'shell' step to run mvn command would work. (will try to move to pipelines for a quick check)

          [JENKINS-40507] maven plugin : build hang when downloading some artifacts

          The version 2.15 of the plugin will bundle the latest version of wagon. Let us know if it helps

          Arnaud Héritier added a comment - The version 2.15 of the plugin will bundle the latest version of wagon. Let us know if it helps

          FYI 2.15.1 is out

          Arnaud Héritier added a comment - FYI 2.15.1 is out

          We experienced the same problem. After looking at Nexus (Support/Metrics) it appeared that 3/4 of the threads were BLOCKED (red). Restarting Nexus seems to fix the problem for us. There is probably a lock somewhere.

          Eric Thiebaut-George added a comment - We experienced the same problem. After looking at Nexus (Support/Metrics) it appeared that 3/4 of the threads were BLOCKED (red). Restarting Nexus seems to fix the problem for us. There is probably a lock somewhere.

            Unassigned Unassigned
            squalou squalou jenkins
            Votes:
            1 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated: