KBEC-00312 - Get Thread dumps in Windows

Article ID:360032827712
1 minute readKnowledge base


You are running into issues where your Commander server is suddenly slowing down or some API requests taking way too long to complete. You need some help narrowing down what could be stalling this operation.


Thread dumps: These are sometimes printed into Commander server logs, but during an issue, its best to get a few of these thread dumps every 30 seconds to 1 minute.

These results will get printed into the commander-service.log and will help narrow down what threads are unavailable or stalled.

How to get Thread dumps

To get the thread dump as explained in https://wrapper.tanukisoftware.com/doc/english/prop-thread-dump-control-code.html do steps below:
1. Run the command:
"sc control CommanderServer 255"
This will log the thread dump to C:\ProgramData\Electric Cloud\ElectricCommander\logs\commander-service.log.
1. Wait for 30 seconds. Note:30 seconds is just an example. Depending on how long the slowness is or if the slowness is due to a burst of requests received by CloudBees CD (CloudBees Flow) server, this may have to be altered to 5 or 10 second intervals. Please follow the interval given by agent. 1. Do step A
1. Do step B and C , 10 more times

All the thread dumps will be logged to the C:\ProgramData\Electric Cloud\ElectricCommander\logs\commander-service.log.

Please send us:

  • Zip and send the commander-service.log file ( and if it rolled over then the recent server*.log.zip file which got rolled over).

  • Commander log files.

NOTE - versions prior to v6.0.4 had service.log as the filename.

See Also

Applies to

  • All Product versions

  • Windows OS versions