KBEC-00298 - Getting the CloudBees CD (CloudBees Flow) Java process thread dump under Linux

Article ID:360032828052
2 minute readKnowledge base


Under normal circumstances, you can get the CloudBees CD (CloudBees Flow) process thread dump by logging into CloudBees CD (CloudBees Flow) and running:

ectool getServerStatus --diagnostics 1

However, if you are trying to troubleshoot a hanging CloudBees CD (CloudBees Flow) process, the process will not be responsive to API commands.


You can get the thread dump directly through Linux commands.

for thread activity analysis, you will need to produce multiple thread dumps spaced a short time apart (typically 30 seconds) in order to properly monitor thread activity over a time span. If support has requested thread dumps from your system, please send 5-10 dumps.

Getting the PID

First, you need to acquire the process ID of the Java service wrapper for CloudBees CD (CloudBees Flow). This PID is stored in the CloudBees CD (CloudBees Flow) directory (/opt/electriccloud/electriccommander by default) under server/commander.pid. E.g. if the file contains the number "964," then the wrapper PID is 964. You can confirm this is the correct PID by running:

ps -ef | grep -i  | grep -i commander | grep -i java

Your output will look something like this:

vagrant  982  964    15  21:51 ?     00:01:12 /opt/electriccloud/electriccommander/jre/bin/java ... (the rest is ommitted)

Note that 982 is the CloudBees CD (CloudBees Flow) child process PID and 964 is the parent wrapper PID we found in commander.pid. Using either the parent or the child PID will produce the same results, as the parent wrapper process simply passes the command to the child Commander process.

Getting the thread dump


kill -3

The -3 option sends the signal that will tell the process to create a thread dump. DO NOT run kill with any other signal option, or you might terminate the CloudBees CD (CloudBees Flow) process.

Repeat this step 5-10 times to get a full set of thread dumps over a time span.

The thread dump is now logged to logs/commander-service.log (or logs/service.log in older versions) in the CloudBees CD (CloudBees Flow) root directory. It can then be cleaned and opened with tools such as Samurai.

Alternative Solution

The thread dump can also be obtained with the JDK jstack utility. This utility can be used on both Linux and Windows machines but may require additional installations. See KBEC-00052 for details on this method.

Applies to

  • Product versions: all

  • OS versions: Linux