Tomcat process does not start on one or more Secondary servers.

Products

• CA Service Management - Service Desk Manager

Issue/Introduction

Tomcat process does not start on one or more Secondary servers.

The stdlog shows the following:
 
[Thread-4] ERROR SLUMP 554 Can't logon to slump - check server daemons: java.lang.IllegalThreadStateException


 

Environment

Service Desk Manager 17.3.x and 17.4.x

Primary and Secondary SDM Servers

Cause

Primary server domsrvr is not available when Tomcat on the secondary server tries to connect

Resolution

In the NX_ROOT\pdm_conf\pdm_startup file we see the following:

; ServiceDesk tomcat
PDM_TOMCAT_CONTROLLER(pdm_tomcat, $NX_LOCAL_HOST, "pdm_tomcat-%h" )
after domsrvr connects + 5

We can increase the + 5 to something larger like + 30, this will ensure that Tomcat waits 30 seconds before trying to connect to the primary domsrvr

This should allow the secondary server Tomcat to connect to the primary server Tomcat after the primary Tomcat has finished starting

Once you have confirmed this is working as intended, be sure to update pdm_startup.tpl similarly so that this change persists whenever pdm_configure is run during upgrades or for any other reason