Deadlocked queue (JENKINS-28840)

Article ID:205009150
1 minute readKnowledge base


You upgraded to 1.609 through to 1.617, your instance doesn’t reply and a threads dump reports a deadlock where one of the deadlocks includes hudson.model.Queue.maintain() and the other deadlocked thread includes Executor like so:

at java.util.concurrent.locks.LockSupport.park(
  at java.util.concurrent.locks.AbstractQueuedSynchronizer.parkAndCheckInterrupt(
  at java.util.concurrent.locks.AbstractQueuedSynchronizer.acquireQueued(
  at java.util.concurrent.locks.AbstractQueuedSynchronizer.acquire(
  at java.util.concurrent.locks.ReentrantLock$NonfairSync.lock(
  at java.util.concurrent.locks.ReentrantLock.lock(
  at hudson.model.Queue._withLock(
  at hudson.model.Queue.withLock(
  at hudson.model.Computer.removeExecutor(
  at hudson.model.Executor.interrupt(


  • CloudBees Jenkins Enterprise 15.05 ( 1.609.1.1 )

  • Jenkins 1.609 -> 1.617


This problem was reported as JENKINS-28840 and is fixed in Jenkins 1.618 (and should be in the LTS 1.609.3).

If you are running CloudBees Jenkins Enterprise 15.05 ( 1.609.1.1 ) please contact the CloudBees Support who will provide you a hotfix for this problem.