Generating a thread dump

Linux/*nix

  1. Get the process id (pid) of the Cascade CMS process by running the command ps aux | grep java. Results will look similar to the following:
    cascade 6415 1.2 67.9 8546368 5203156 ? Sl Jun28 635:49 /usr/local/cascade/java/jre/bin/java ...

    In this example, 6415 is the pid we're looking for.

  2. Execute the following command to send a kill signal to the Cascade CMS process: kill -3 <pid>

    Continuing the example from above, the command will be: kill -3 6415
Note: This particular kill signal will not stop the application. It will simply output a thread dump within the tomcat/logs/catalina.out file.

Windows (using PowerShell)

  1. First, open Task Manager in Windows.
  2. Locate the PID of the running Cascade CMS process and keep it handy (tomcat9.exe, for example, as seen below):

    cascade-pid.png

  3. Open PowerShell using the Run as Administrator option.
  4. Change directories into the java\bin folder. For example: cd C:\Program Files\Cascade CMS\java\jdk\bin
  5. Execute a command like the one below making sure to replace the <PID> with the PID of the running Cascade CMS process:
    jcmd <PID> Thread.print > cascade-thread-dump-dd-mm-yyyy.log

The thread dump will be generated in the file you've specified in the command directly above.

Windows (using Tomcat Monitor Service)

  1. Open a command prompt using the Run as Administrator option.
  2. Change directories into the tomcat/bin folder. For example: cd C:\Program Files\Cascade CMS\tomcat\bin
  3. Enter the command: CascadeCMSw //MS//
    The Tomcat Monitor Service icon will appear in the system tray:
    tomcat-monitor-icon.png
  4. Right-click the Tomcat Monitor Service icon, then select Thread Dump.
Note: Performing this action will not stop the application. The thread dump will be added to the tomcat/logs/cascadecms-stdout.{date} file.