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

Multiple build jobs are the waiting queue waiting to next available excutor, but no build jobs are running. Appears after migration from ver 1.606 to 1.609

    XMLWordPrintable

    Details

    • Similar Issues:

      Description

      Just migrated from Jenkins 1.606 to 1.609

      One build jobs started simultaneously 8 downstream jobs.
      All 8 jobs are in the waiting queue waiting for next available executor for very long time (hours!) but there is no one executor is running from total four!

        Attachments

          Activity

          Hide
          danielbeck Daniel Beck added a comment -

          How are the downstream jobs started?

          Show
          danielbeck Daniel Beck added a comment - How are the downstream jobs started?
          Hide
          gremlm Grigoriy Milman added a comment -

          I have reproduced the error again:

          Job A has been started by manually and executed.

          After execution it triggered ((placed to the queue) another 3 build jobs.
          At the same time other 5 build jobs have been triggered (placed to the queue) by SCM, 4 of the last 5 jobs are downstream to the first 3 build jobs but one independent (does not have upstream job at all)!

          No job except job A has been processed. all other are in the queue for ever.

          By the way there are multiple strange log entries in jenkins.err.log like the following

          Apr 17, 2015 9:19:45 AM hudson.triggers.SafeTimerTask run
          SEVERE: Timer task hudson.model.Queue$MaintainTask@f79885 failed
          java.lang.NullPointerException
          at jenkins.advancedqueue.sorter.AdvancedQueueSorter$2.compare(AdvancedQueueSorter.java:99)
          at jenkins.advancedqueue.sorter.AdvancedQueueSorter$2.compare(AdvancedQueueSorter.java:81)
          at java.util.Arrays.mergeSort(Unknown Source)
          at java.util.Arrays.sort(Unknown Source)
          at java.util.Collections.sort(Unknown Source)
          at jenkins.advancedqueue.sorter.AdvancedQueueSorter.sortBuildableItems(AdvancedQueueSorter.java:81)
          at hudson.model.Queue.maintain(Queue.java:1337)
          at hudson.model.Queue$MaintainTask.doRun(Queue.java:2435)
          at hudson.triggers.SafeTimerTask.run(SafeTimerTask.java:51)
          at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source)
          at java.util.concurrent.FutureTask$Sync.innerRunAndReset(Unknown Source)
          at java.util.concurrent.FutureTask.runAndReset(Unknown Source)
          at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$101(Unknown Source)
          at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.runPeriodic(Unknown Source)
          at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(Unknown Source)
          at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown Source)
          at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
          at java.lang.Thread.run(Unknown Source)

          Show
          gremlm Grigoriy Milman added a comment - I have reproduced the error again: Job A has been started by manually and executed. After execution it triggered ((placed to the queue) another 3 build jobs. At the same time other 5 build jobs have been triggered (placed to the queue) by SCM, 4 of the last 5 jobs are downstream to the first 3 build jobs but one independent (does not have upstream job at all)! No job except job A has been processed. all other are in the queue for ever. By the way there are multiple strange log entries in jenkins.err.log like the following Apr 17, 2015 9:19:45 AM hudson.triggers.SafeTimerTask run SEVERE: Timer task hudson.model.Queue$MaintainTask@f79885 failed java.lang.NullPointerException at jenkins.advancedqueue.sorter.AdvancedQueueSorter$2.compare(AdvancedQueueSorter.java:99) at jenkins.advancedqueue.sorter.AdvancedQueueSorter$2.compare(AdvancedQueueSorter.java:81) at java.util.Arrays.mergeSort(Unknown Source) at java.util.Arrays.sort(Unknown Source) at java.util.Collections.sort(Unknown Source) at jenkins.advancedqueue.sorter.AdvancedQueueSorter.sortBuildableItems(AdvancedQueueSorter.java:81) at hudson.model.Queue.maintain(Queue.java:1337) at hudson.model.Queue$MaintainTask.doRun(Queue.java:2435) at hudson.triggers.SafeTimerTask.run(SafeTimerTask.java:51) at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source) at java.util.concurrent.FutureTask$Sync.innerRunAndReset(Unknown Source) at java.util.concurrent.FutureTask.runAndReset(Unknown Source) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$101(Unknown Source) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.runPeriodic(Unknown Source) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) at java.lang.Thread.run(Unknown Source)
          Hide
          danielbeck Daniel Beck added a comment -

          Looks like a bug in Priority Sorter plugin.

          Show
          danielbeck Daniel Beck added a comment - Looks like a bug in Priority Sorter plugin.
          Hide
          emsa23 Magnus Sandberg added a comment -

          Are you using 2.12?

          Show
          emsa23 Magnus Sandberg added a comment - Are you using 2.12?
          Hide
          gremlm Grigoriy Milman added a comment -

          We are using 2.11
          It could be the same issue as in JENKINS-27957, so I will try 2.12, may be it is already fixed.
          I will try it today.

          Show
          gremlm Grigoriy Milman added a comment - We are using 2.11 It could be the same issue as in JENKINS-27957 , so I will try 2.12, may be it is already fixed. I will try it today.
          Hide
          gremlm Grigoriy Milman added a comment - - edited

          It looks like it is duplicate of the JENKINS-27957
          Version 2.12 which has a fix for the JENKINS-27957 does not repeat the problem

          Show
          gremlm Grigoriy Milman added a comment - - edited It looks like it is duplicate of the JENKINS-27957 Version 2.12 which has a fix for the JENKINS-27957 does not repeat the problem
          Hide
          emsa23 Magnus Sandberg added a comment -

          Great

          Show
          emsa23 Magnus Sandberg added a comment - Great

            People

            Assignee:
            emsa23 Magnus Sandberg
            Reporter:
            gremlm Grigoriy Milman
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved: