Cisco Bug: CSCvh82567 - Customer: Simultaneous crashes on two different servers with 'server!ServerApp1Cmgr::process_pending
May 30, 2018
- Cisco Meeting Server
Known Affected Releases
Symptom: CMS server Module 0 crashes when looking up a call/conference GUID for a message that can't be resolved. Conditions: This can occur as a result of a race condition/timing issue where the call/conference GUID no longer exists (due to conferences/calls being disconnected and destroyed) and an associated message item is queued up for that call/conference. So when the message is eventually processed, the look up fails and instead of gracefully handling this scenario, the CMS server crashes.
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)
- Known Fixed Releases
- Related Community Discussions
- Number of Related Support Cases