Cisco Bug: CSCul43593 - Cisco Tomcat Service remains in a starting state
Last Modified
Jan 18, 2021
Products (1)
- Cisco Unified Communications Manager IM & Presence Service
Known Affected Releases
10.0(1)
Description (partial)
Symptom: After a restart of the Cisco Unified Communications Manager Instance Messaging and Presence server, the Cisco Tomcat service is not starting up. This following error is observed in the Cisco Tomcat catalina.out log file: Still running according to PID file /usr/local/thirdparty/jakarta-tomcat/conf/tomcat.pid, PID is 10727 Service exit with a return value of 122 The log file viewable using the following Admin CLI command: file view activelog tomcat/logs/catalina.out Conditions: The issue has been observed intermittently in the following situations: After completing an install of the Cisco Unified Communications Manager Instance Messaging and Presence server After a System Restore of the Cisco Unified Communications Manager Instance Messaging and Presence server Cisco Tomcat service restart
Bug details contain sensitive information and therefore require a Cisco.com account to be viewed.
Bug Details Include
- Full Description (including symptoms, conditions and workarounds)
- Status
- Severity
- Known Fixed Releases
- Related Community Discussions
- Number of Related Support Cases