Cisco Bug: CSCul29603 - Tomcat HTTPS port inaccessible due to HTTPS thread pool exhaustion
Last Modified
Feb 19, 2018
Products (3)
- Cisco Unified Communications Manager (CallManager)
- Cisco Intercompany Media Engine
- Cisco Unified Communications Manager Version 10.0
Known Affected Releases
10.0(1)
Description (partial)
Symptom: Applications running in Cisco Tomcat thats accessible over HTTPS on CUCM or CUCM IM&P not accessible. Jabber login failure on CUCM IM&P. Conditions: All of Tomcat's HTTPs ports are consumed/exhausted Running "utils diagnose test" from admin CLI & verifying the diagnostics output file (file view activelog platform/log/diag1.log), running from CUCM, you would see in the following section on CUCM 11-08-2013 11:51:50 tomcat_threads: Checking for busy HTTPS threads... 11-08-2013 11:51:52 tomcat_threads: HTTPS threads: [150] Running from IM&P, you would see 11-08-2013 11:51:50 tomcat_threads: Checking for busy HTTPS threads... 11-08-2013 11:51:52 tomcat_threads: HTTPS threads: [200]
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