How to take a thread dump in ConnectALL

Products

• ConnectALL

Issue/Introduction

This article documents the steps needed to take a thread dump to identify issues in ConnectALL.

Environment

3.0 and higher

 

Resolution

These steps assume that a Java Development Kit (JDK) is already installed

 

Linux

Open an ssh session to your ConnectALL server and run the following command:

pgrep -f connectall-core.jar | awk '{print $1}' | xargs jstack $1 > threaddump.txt

Collect the created threaddump.txt file and attach it to your support ticket.

 

Windows

Identifying the process

First, it will be necessary to identify the process ID (PID) of the core service.

To do this, open Task Manager and add the column for "Command Line"

Identifying the process that relates to the core service will require careful examination of the java.exe processes. 

There are three ConnectALL java.exe processes.  Your system may have additional java.exe processes if it is running other Java based applications.

Look for the java.exe processes that mention ConnectALL in the Command Line column

Then you need to exclude the process that references "Scheduler" and exclude the process that references "artemis" in the Command Line.

What you are left with is the PID for the Core service.  Note this for the below step.

 

Running jstack.exe

Open a command prompt

Using the PID determined above run the following command:

jstack.exe #### > threaddump.txt

If no errors appear then gather the threaddump.txt file and attach it to your support ticket.

 

If you receive the following error:

'jstack.exe' is not recognized as an internal or external command,
operable program or batch file.

Then jstack.exe is not in your path you will need to locate it and execute the steps above directly from the JDK bin directory.

 

Locating jstack.exe

If the %JAVA_HOME% environment variable is set you can simply open a File Explorer window and type %JAVA_HOME%bin into the address bar and it will take you there

 

Otherwise, if you installed the OpenJDK from Microsoft's website then it will possibly be in C:\Program Files\Microsoft\jdk-xx.x.xx.xx-xxxxxx\bin and you can try to browse to this location using the File Explorer

Once you have located the correct folder, replace the contents of the address bar with "cmd" and press enter

This will open a cmd prompt in the correct location to run 

Now you can proceed to run the jstack.exe command as indicated above.