Troubleshooting

Generating a thread dump

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

First, open Task Manager in Windows.
Locate the PID of the running Cascade CMS process and keep it handy (tomcat9.exe, for example, as seen below):
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
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.