Preview Tool

Cisco Bug: CSCvs62938 - CUMI: JNI Call leading to Performance Bottleneck leading to Tomcat 503 with huge voice messages

Last Modified

Jan 13, 2020

Products (1)

  • Cisco Unity Connection

Known Affected Releases

11.5 12.5 14.0

Description (partial)

Below series of symptoms can be observed for this issue on Server side
1- Tomcat Publisher or Subscriber may get huge no . of 503 (server busy) error messages
2- Tomcat threads started to get stuck and other request been queued increasing tomcat memory and CPU
3- Tomcat sluggishness and eventually crash could be observed as a result of above points

Below series of symptoms can be observed for this issue on Client (Jabber) side
1- Jabber could misbehave and could cause multiple subscription as 503 on both node impacts jabber creating new session with unity server
2- More rate of VMrest request as jabber connects to server each time due to 503
3- Jabber keeps on having message "Cannot cannot to Voicemail . Contact your system Administrator"

Bottleneck is for single API call also but becomes more prevalent under below conditions 
1- Customer have mailboxes with high no of voice messages say 500-1000 
2- Jabber integrated with unity and invokes "/vmrest/mailbox/folders/inbox/messages" to fetch voice mails  

As of now bottleneck is observed only for "/vmrest/mailbox/folders/inbox/messages" API call
Bug details contain sensitive information and therefore require a 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.