As a short-term solution, you could run the following commands, consecutively, on the server:
pdm_tomcat_nxd -d stop
pdm_tomcat_nxd -d start
For a long-term solution, determine the difference in timestamps between the messages described in symptom #4. And, then, configure a delay time that is longer than the difference.
To configure the delay, modify the pdm_startup file as follows:
- Find the section that starts with:
PDM_TOMCAT_CONTROLLER(pdm_tomcat, $NX_LOCAL_HOST, "pdm_tomcat-%h" )
- In an out-of-the-box environment, the next line would contain this statement:
after domsrvr connects + 5
- Change "after domsrvr connects + 5" to "after domsrvr connects + 120". Alternatively, instead of 120 seconds, set a value for the number of seconds that is slightly higher than the earlier-computed timestamps difference.
For the change to persist, be sure to make the same modification to the pdm_startup.tpl file.
After configuring the pdm_startup file, recycle the CA Service Desk Manager services. Do this on each affected CA SDM server in the environment. Be sure to recycle according to the requirements of the appropriate configuration type: Conventional (primary, secondary) or Advanced Availability (background, standby, application).