Cisco Bug: CSCvt29418 - Lightweight AP status thread is taking a longer time to complete an iteration
Oct 08, 2020
- Cisco Prime Infrastructure
Known Affected Releases
Symptom: Sometimes, when the logging level is set to debug, the logs may report deadlocks while updating the apUpTime, due to a large number of APs in the setup, and Prime Infrastructure slowness. When APs are receiving associated payload from the device, and at the same time, the APUpTime background job are both trying to modify the related tables by acquiring locks. Conditions: This was observed in Prime Infrastructure 3.7.
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