Guest

Preview Tool

Cisco Bug: CSCvh92884 - Jabber chooses TC-Service according to "Cluster ID" rather than load balancing when creating rooms

Last Modified

Sep 18, 2019

Products (1)

  • Cisco Jabber for Windows

Known Affected Releases

11.9(2) 11.9(3)

Description (partial)

Symptom:
When creating a persistent chat room in Jabber, and you chose "Automatically Select" option for location, the client will check the "Cluster ID" which the user belongs to, and would pick the first TC-Service according to "Cluster ID". It would be better for the stability of the database if the client would load balance when choosing the TC-Service. In a multi-cluster environment this leads to one db in a particular cluster having the majority of the load in terms of rooms and traffic. This also occurs in a single cluster environment.

Conditions:
Jabber 11.9.2
Persistent Chat configured with an External DB. 
Create a room with the "Location" set to "Automatically Select"
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.