Comments

• 
  Suresh Venkatesan August 13, 2015 18:09

  Actually the above KB article just mentions how to get one thread dump logged to the logs/service.log in the Commander directory. But to analyze we need multiple thread dumps as mentioned below:

  A.The ProcessID of the Commander wrapper process is stored in /opt/electriccloud/electriccommander/server/commander.pid file In this file if you see the content is "1052" that means the Commander wrapper process ID is 1052.
  B.Run the command from the shell prompt:kill -3 <PID_in_/opt/electriccloud/electriccommander/server/commander.pid>For example if the PID is 1052 run:"kill -3 1052"

  Similarly the agent thread dump can be got using <PID_in_/opt/electriccloud/electriccommander/logs/agent/agent.pid>

  C.Wait for 30 seconds ( or longer if the issue or hang is for a longer duration . For example: like 1 or 2 minutes if the issue is related to commander not logging to commander.log )

  D.Do step B

  E. Do step C and D , 10 times

  All the thread dumps will be logged to the /opt/electriccloud/electriccommander/logs/service.log

  Please send the following to Electric Cloud Support :
  1.Zip and send the service.log file ( and if it rolled over then the recent server*.log.zip file which got rolled over).
  2. Commander log files.

  Here are the steps for Windows platform:

  To get the thread dump as explained in http://wrapper.tanukisoftware.com/doc/english/prop-thread-dump-control-code.html do steps below:
  A.Run the command:
  "sc control CommanderServer 255"
  This will log the thread dump to C:\ProgramData\Electric Cloud\ElectricCommander\logs\service.log.
  B.Wait for 30 seconds ( or longer if the issue or hang is for a longer duration . For example: like 1 or 2 minutes if the issue is related to commander not logging to commander.log ).
  C.Do step A
  D. Do step B and C , 10 times

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

  Please send the following to Electric Cloud Support :
  1.Zip and send the service.log file ( and if it rolled over then the recent server*.log.zip file which got rolled over).

  2. Commander log files.