Linux/*nix

  • 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.

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

In this example, 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 Tomcat Monitor Service)

  • Open a command prompt using the Run as Administrator option 
  • Change directories into the tomcat/bin  folder. For example: 
cd C:\Program Files\Cascade CMS\tomcat\bin
  • Enter the command CascadeCMSw //MS//
  • A Tomcat Monitor Service icon will appear in the system tray:
  • 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

Windows (using PowerShell)

  • Open PowerShell using the Run as Administrator option 
  • Change directories into the java\bin  folder. For example: 
cd C:\Program Files\Cascade CMS\java\jdk\bin
  • Run the following command:
jps -l -m -v
  • Locate the process id (PID) from the output of that command. Example:
  • Substitute the PID into the following command and execute it:
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.

Did this answer your question?