Skip to main content

Generating a thread dump

A thread dump captures what every thread in the application is doing at one moment. Support may ask for one when the application is slow or appears hung.

Linux, *nix, and macOS

  1. Get the process id (pid) of the Cascade CMS process:

    Bash
    ps aux | grep java

    Results look similar to the following, where 6415 is the pid:

    Bash
    cascade 6415 1.2 67.9 8546368 5203156 ? Sl Jun28 635:49 /usr/local/cascade/java/jre/bin/java ...
  2. Send a kill signal to that process:

    Bash
    kill -3 6415

This kill signal does not stop the application. It writes a thread dump into tomcat/logs/catalina.out.

Windows, using PowerShell

  1. Open Task Manager.
  2. Locate the PID of the running Cascade CMS process — tomcat9.exe, for example:

    Cascade CMS process id shown in Windows Task Manager

  3. Open PowerShell using Run as Administrator.
  4. Change into the java\bin folder, for example:

    Bash
    cd 'C:\Program Files\Cascade CMS\java\jdk\bin'
  5. Run the following, replacing <PID> with the pid you noted:

    Bash
    ./jcmd <PID> Thread.print > cascade-thread-dump-dd-mm-yyyy.log

The thread dump is written to the file you named in that command.