Sometimes Service Desk application has intermittent pdm_tomcat_nxd process crash. Follows Some steps to take care and prevent this occurrence.
This document describes how to recover in the event that the Service Desk Tomcat stops functioning. Tomcat should not crash. However, this document describes how to recover.
Service Desk 12.7, 12.9
- If you notice that tomcat is no longer functioning, first open "Task Manager" and verify that javaw.exe and pdm_tomcat_nxd.exe are running (if you are not running on a Windows platform, you may use the appropriate:
"ps -ef | grep -i <name>" command.
If either has stopped running check the system for any dump files (if configured) and please archive the Service Desk\log\ folder before proceeding (very important).
You may open a CA Support issue to help analyze the data.
- Go into the bopcfg\www\CATALINA_BASE\temp directory, if there are any files in there note how many, and clear the directory out. If there are several hundreds or thousands of files this could cause a problem. After clearing the files try to manually kill the javaw.exe first and then the pdm_tomcat_nxd.exe process.
- If killing the javaw.exe and pdm_tomcat_nxd.exe processes does not bring up Tomcat, open up a command prompt and run the following command:
Find any pdm_tomcat entries in the list, note the date associated with the process, if the time appears old, then the tomcat process may be stuck in slump
- From the slstat list get the exact name of the process, it may be something like "pdm_tomcat-*servername*" take the exact name and run the following command from a prompt:
This will disconnect the process from slump
(Service Desk Manager's messaging daemon).
- Next run, the following commands:
pdm_tomcat_nxd -d stop
pdm_tomcat_nxd -d start
pdm_tomcat_nxd -c stop
pdm_tomcat_nxd -c start
- If the cause of the crash is not known, please open a support issue and provide the following from the server where the Service Desk Tomcat crashed
12.7, 12.9 and later releases:
Switch to the diag\bin\ folder:
Run the following command:
supp_diag.cmd (or *.sh)
This will create an archive file that can be attached to the Support Case.