I'm testing the google-compute-engine-plugin and it seems there are a bunch of blocked threads related to the below hudson.remoting methods:
- hudson.remoting.Request.call(Request.java:154) - hudson.remoting.Channel.send(Channel.java:716) See some of the stacktraces: Computer.threadPoolForRemoting [#414] priority:5 - threadId:0x00007f848800c000 - nativeId:0x1c73 - nativeId (decimal):7283 - state:BLOCKED stackTrace: java.lang.Thread.State: BLOCKED (on object monitor) at hudson.remoting.Request.call(Request.java:154) - waiting to lock <0x00000007b6b39490> (a hudson.remoting.Channel) at hudson.remoting.Channel.call(Channel.java:954) at hudson.slaves.SlaveComputer.setChannel(SlaveComputer.java:624) at hudson.slaves.SlaveComputer.setChannel(SlaveComputer.java:418) at com.google.jenkins.plugins.computeengine.ComputeEngineComputerLauncher.launch(ComputeEngineComputerLauncher.java:318) at com.google.jenkins.plugins.computeengine.ComputeEngineComputerLauncher.launch(ComputeEngineComputerLauncher.java:224) at hudson.slaves.SlaveComputer.lambda$_connect$0(SlaveComputer.java:290) at hudson.slaves.SlaveComputer$$Lambda$378/348978491.call(Unknown Source) at jenkins.util.ContextResettingExecutorService$2.call(ContextResettingExecutorService.java:46) at jenkins.security.ImpersonatingExecutorService$2.call(ImpersonatingExecutorService.java:71) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) at java.lang.Thread.run(Thread.java:748) Computer.threadPoolForRemoting [#347] for obs11-linux-r6rpli id=25 priority:5 - threadId:0x00007f849427b000 - nativeId:0x1a93 - nativeId (decimal):6803 - state:BLOCKED stackTrace: java.lang.Thread.State: BLOCKED (on object monitor) at hudson.remoting.Channel.send(Channel.java:716) - waiting to lock <0x00000006d82e4570> (a hudson.remoting.Channel) at hudson.remoting.Request$2.run(Request.java:382) at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72) at org.jenkinsci.remoting.CallableDecorator.call(CallableDecorator.java:18) at hudson.remoting.CallableDecoratorList$1.call(CallableDecoratorList.java:21) at jenkins.util.ContextResettingExecutorService$2.call(ContextResettingExecutorService.java:46) at jenkins.security.ImpersonatingExecutorService$2.call(ImpersonatingExecutorService.java:71) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) at java.lang.Thread.run(Thread.java:748) *Environment:* - Docker Jenkins instance. - Jenkins Version 2.109 - Trilead-api 1.05 - Testing PR: https://github.com/jenkinsci/google-compute-engine-plugin/pull/183 - Reported as an issue in the Google Compute Engine plugin: https://github.com/jenkinsci/google-compute-engine-plugin/pull/184 I created a few dumps and uploaded them to https://fastthread.io/: - https://fastthread.io/my-thread-report.jsp?p=c2hhcmVkLzIwMjAvMDIvMTAvLS1vdXRwdXQtMi5sb2ctLTEyLTEwLTU5OzstLW91dHB1dC0xLmxvZy0tMTItMTAtNTk7Oy0tb3V0cHV0LmxvZy0tMTItMTAtNTk= *Questions:* - Have you seen that particular behaviour? - Any clues how I can debug it further? - Is that an expected behaviour in the remoting itself? Or a kind of bug? Thanks -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/9536ac07-203f-48f6-b719-53d9213c0faa%40googlegroups.com.
