"Tomcat was stopped" messages appear in the stdlog intermittently due to unload or redeploy


Article ID: 192527


Updated On:


CA Service Desk Manager CA Service Desk Manager - Unified Self Service KNOWLEDGE TOOLS


Tomcat intermittently and unexpectedly fails on the servers.

For example, in a windows environment, check the stdlog.x files under "C:\Program Files (x86)\CA\Service Desk Manager\log" for a messages similar to:

05/21 18:50:38.81 sdmapp01  pdm_tomcat           2536 SIGNIFICANT  pdm_tomcat.c          1047 SERVICEDESK Tomcat was stopped on Thu May 21 18:50:38 CEST 2020

In the pdm_tomcat.log, one of the following messages is written:

org.apache.catalina.startup.HostConfig reload

org.apache.catalina.startup.HostConfig undeploy


Tomcat is configured such that changes made to particular configuration files whilst it is running cause Tomcat to be reloaded or redeployed.


Release : 17.2



1. Determine if any changes have been made to any files that could trigger a reload or reploy of Tomcat after it is up and running. 
2. Explicitly configure "autoDeploy=false" and "reloadable=false" for Tomcat.
3. Check for any possible relevant duplicate jar files or soft links on the server and consider replacing them with a copy of the associated file.
4. Ensure that Tomcat Manager is not being used to make changes to Tomcat files whilst Tomcat is up and running.
5. Consider using a tool like fswatch to monitor file changes in specific locations.
6. Turn on debug for Tomcat (Run: pdm_log4j_config -f SDM_WEB -l DEBUG -a -s 30MB ) and the Service Desk Manager pdm_logstat trace for tomcat.c (Run: pdm_logstat -f tomcat.c 301 )

Additional Information

1. https://www.mulesoft.com/tcat/tomcat-reload
2. https://tomcat.apache.org/tomcat-8.0-doc/deployer-howto.html
3. https://ci.apache.org/projects/tomcat/tomcat85/docs/manager-howto.html