Guest

Preview Tool

Cisco Bug: CSCtd71191 - PMR 19684 49R Tomcat services not accessible waiting on DB connto Pub

Last Modified

Jan 30, 2017

Products (1)

  • Cisco Unified Communications Manager (CallManager)

Known Affected Releases

8.0(0.99121.6)

Description (partial)

Symptom:
CUCM Admin, CUCM User or any other https connection is timing out. Tomcat Service logs indicates

 Nov 30, 2009 4:07:26 PM org.apache.tomcat.util.net.JIoEndpoint createWorkerThread
INFO: Maximum number of threads (150) created for connector with address null and port 8443

After a communication problem between the Publisher and Subscriber node, Tomcat Web services are no longer functional eventhough the service is up.

Utils diagnose test on tomcat_connectors module confirms the HTTPS port is no longer responding.

In the Catalina.out file you can observe Tomcat Services ran out of Threads.

Nov 30, 2009 4:07:26 PM org.apache.tomcat.util.net.JIoEndpoint createWorkerThread
INFO: Maximum number of threads (150) created for connector with address null and port 8443

Conditions:
When Publisher to Subscriber communication is interrupted under certain condition the DB connections from Tomcat/Java services gets hung. This leads to Tomcat running out maximum threads and stop processing any new requests.
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
Bug information is viewable for customers and partners who have a service contract. Registered users can view up to 200 bugs per month without a service contract.