Guest

Preview Tool

Cisco Bug: CSCvt31323 - CUNI : Notification to callback URL's stop working because Socket Read Timeout Not implemented

Last Modified

Aug 26, 2020

Products (1)

  • Cisco Unity Connection

Known Affected Releases

11.5

Description (partial)

Symptom:
Below are clear symptoms which should be refereed while matching this defect

1) CUNI subscriptions events are not sent anymore to any callback URL leading to business outages for CUNI
2) Take Notifier thread dump using command (exclude single quotes)  "kill -3 $(ps -ef | grep "CuNotifier" | grep -v 'grep' | grep -v 'sudo' | awk '{print $2}')" on the node which has Primary role (CuNotifier is running)
3) Open file at /var/log/active/cuc with name CuNotifierThreadDump.txt and serach for latest timestamp usually EOF
4) Check if we have same thread dump experienced mentioned in defects symptoms then only you are hitting this defect and attach SR to the defect 


#######################
For all other scenarios not matching above symptoms , we are not hitting this defect and troubleshooting needs to be performed further to isolate RCA

Conditions:
Issue is observed for one of biggest customer deployment under below conditions-( Refer Enclosures for Diagram of the Deployment)

Finding Till Date (Customer environment)- 

We have found issue based on PCAP analysis due to below reasons -
- Network congestion and packet not able to be received by unity on port opened for communication by CUNI URL
- High Packet Re-transmission due to Web-service inability to close the connection with server properly

RCA for above findings :
- Issue is accepted on client side resetting the connection w/o waiting for server FIN/ACK
- There has been more finding on client side and approaches are well decided on ability to wait for Server FIN/ACK for graceful shutdown
- They are calling direct close() leaving the socket is close_wait() state on server

##################################################################
To Reproduce the same behavior in lab - Refer to defect enclosures on steps to reproduce the issue
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.