Guest

Preview Tool

Cisco Bug: CSCuj07379 - If 274 autoreg events are submitted to Voss within one second, Voss s

Last Modified

Jan 12, 2014

Products (1)

  • Cisco Hosted Collaboration Solution (HCS)

Known Affected Releases

8.1(2)ER1

Description (partial)

Symptom:
Details:
If any device using syslog to submit events sends 274 such events to our
syslog. Our bvsmbatch queue on http://127.0.0.1:81/ stops responding. Therefore
Voss as a whole appears to the customer as having "crashed".

Prerequisites:
1.A Voss system
2.A device submitting events through Syslog.
3.274 events to submit through syslog.

Steps to Reproduce:
1.Arrange that a device using syslog to submit events to us submits 274 events
within one second.
2.Watch Voss stop responding to further queue requests after apache has reached
283 processes.
3.
4.
5.
6.
Actual Results:  
Voss stops responding to any further requests such as logins, registrations,
phone directory or phone login requests.

Expected Results:  
Voss should handle a saturated queue with some kind of "push-back" instead of
just ignoring everything.

Workaround Available: Unsure
Workaround Steps:
1.Fail over if a cluster, restart all services if standalone.
2.
3.
4.
5.
6.

Conditions:
Details:
If any device using syslog to submit events sends 274 such events to our
syslog. Our bvsmbatch queue on http://127.0.0.1:81/ stops responding. Therefore
Voss as a whole appears to the customer as having "crashed".

Prerequisites:
1.A Voss system
2.A device submitting events through Syslog.
3.274 events to submit through syslog.

Steps to Reproduce:
1.Arrange that a device using syslog to submit events to us submits 274 events
within one second.
2.Watch Voss stop responding to further queue requests after apache has reached
283 processes.
3.
4.
5.
6.
Actual Results:  
Voss stops responding to any further requests such as logins, registrations,
phone directory or phone login requests.

Expected Results:  
Voss should handle a saturated queue with some kind of "push-back" instead of
just ignoring everything.

Workaround Available: Unsure
Workaround Steps:
1.Fail over if a cluster, restart all services if standalone.
2.
3.
4.
5.
6.
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.