-
Bug
-
Resolution: Unresolved
-
Critical
-
None
We got a rather interesting situation when we see cpu, memory and high disk performance in access, but at the same time we see the AtmostOneTaskExecutor thread freezing, which blocked all the others, as a result, after a while, we lost access to the web interface and were forced to restart the service
"AtmostOneTaskExecutor[Periodic Jenkins queue maintenance] [#37532]" #1990238 daemon prio=5 os_prio=0 tid=0x00007f243416f800 nid=0x8be runnable [0x00007f22d1959000]"AtmostOneTaskExecutor[Periodic Jenkins queue maintenance] [#37532]" #1990238 daemon prio=5 os_prio=0 tid=0x00007f243416f800 nid=0x8be runnable [0x00007f22d1959000] java.lang.Thread.State: RUNNABLE at com.cloudbees.hudson.plugins.folder.computed.ThrottleComputationQueueTaskDispatcher.computationCount(ThrottleComputationQueueTaskDispatcher.java:170) at com.cloudbees.hudson.plugins.folder.computed.ThrottleComputationQueueTaskDispatcher.computationCount(ThrottleComputationQueueTaskDispatcher.java:130) at com.cloudbees.hudson.plugins.folder.computed.ThrottleComputationQueueTaskDispatcher.canRun(ThrottleComputationQueueTaskDispatcher.java:98) at hudson.model.Queue.getCauseOfBlockageForItem(Queue.java:1203) at hudson.model.Queue.maintain(Queue.java:1533) at hudson.model.Queue$1.call(Queue.java:333) at hudson.model.Queue$1.call(Queue.java:330) at jenkins.util.AtmostOneTaskExecutor$1.call(AtmostOneTaskExecutor.java:108) at jenkins.util.AtmostOneTaskExecutor$1.call(AtmostOneTaskExecutor.java:98) at jenkins.security.ImpersonatingExecutorService$2.call(ImpersonatingExecutorService.java:71) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at hudson.remoting.AtmostOneThreadExecutor$Worker.run(AtmostOneThreadExecutor.java:111) at java.lang.Thread.run(Thread.java:748) Locked ownable synchronizers: - <0x0000000246ae2f88> (a java.util.concurrent.locks.ReentrantLock$NonfairSync)
