Cisco Bug: CSCuj34533 - UpdateEvent ignored by Paused Event
May 03, 2017
- Cisco Broadband Access Center for Telco and Wireless
Known Affected Releases
Symptom: While a execution of CRSUpdateEvent is in progress, if a CRSPausedEvent is received OR while a CRSPausedEvent is in progress if a CRSUpdateEvent is received, the CRSUpdateEvent would be ignored. As a result of that, CRS statistics (including the information related to currently executing request, number of pending requests etc) returned by getRDUDetails API or displayed on the CRS page in adminUI would not be in synch with the database, until CRS receives another CRSUpdateEvent or CRS is resumed (whichever takes place earlier). Conditions: This might happen only in a highly concurrent environment where multiple API clients are trying to add CRS requests to the queue as well as pausing CRS together.
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