Is it possible to recycle Tomcat without restarting the entire Service Desk Manager application?

Products

• CA Service Desk Manager
• CA Service Management - Service Desk Manager

Issue/Introduction

Is it possible to recycle Tomcat without restarting the entire Service Desk Manager Service?

Environment

Service Desk Manager 17.3

All Supported Operating Systems

Resolution

It is possible to restart the Tomcat process without fully restarting Service Desk Manager services.

This can be done through a command prompt.

Open a command prompt "As Administrator" and run the following commands:

pdm_tomcat_nxd -c stop

(this stops the Tomcat container)

pdm_tomcat_nxd -c start

(this will start the Tomcat container)

If you wish to restart to daemon completely you can use the commands:

pdm_tomcat_nxd -d stop

pdm_tomcat_nxd -d start

You can then use this command to check the status and startup time of the service

pdm_tomcat_nxd -c status

The commands outlined above will only stop and start the primary Service Desk Manager Tomcat, but a similar command also exists for other Tomcat instances

For CMDB Visualizer:

pdm_tomcat_nxd -c stop -t VIZ

pdm_tomcat_nxd -c start -t VIZ

For Support Automation:

pdm_tomcat_nxd -c stop -t SA

pdm_tomcat_nxd -c start -t SA

For Restful Web Services:

pdm_tomcat_nxd -c stop -t REST

pdm_tomcat_nxd -c start -t REST

For Federated Search:

pdm_tomcat_nxd -c stop -t FS

pdm_tomcat_nxd -c start -t FS

Additional Information

In order to tell if Tomcat is accessible, one can run 

netstat -ano | findstr 8443
netstat -ano | findstr 8080

The above will generate a netstat result showing all connections made to port 8443 (Tomcat Default SSL config) or port 8080 (Tomcat default non-SSL config).  An output of 8080 may not be presented if Tomcat non-SSL was disabled.

One may see an output such as this:

C:\>netstat -ano | findstr 8443
  TCP    0.0.0.0:8443           0.0.0.0:0              LISTENING       1234
  TCP    XXX.XXX.XXX.XXX:8443   XXX.XXX.XXX.XXX:XXX    FIN_WAIT_2      1234
  TCP    XXX.XXX.XXX.XXX:8443   XXX.XXX.XXX.XXX:XXX    FIN_WAIT_2      1234
  TCP    XXX.XXX.XXX.XXX:8443   XXX.XXX.XXX.XXX:XXX    FIN_WAIT_2      1234
  TCP    [::]:8443              [::]:0                 LISTENING       1234

If the highlighted entries are not present, or no output is returned at all, that means Tomcat is down or not listening on port 8443, which may be of interest if one is troubleshooting Tomcat.  If port access still presents in an issue with Tomcat, that means something else may be a problem with Tomcat accesibility.

A restart of Tomcat per the above will generate a new PID (highlighted below in comparison to prior example run):

C:\>netstat -ano | findstr 8443
  TCP    0.0.0.0:8443           0.0.0.0:0              LISTENING       5678
  TCP    [::]:8443              [::]:0                 LISTENING       5678