Cisco Bug: CSCut14797 - Enhance RisDC throttling thread to resume suspended threads after crash
May 05, 2016
- Cisco Unified Communications Manager (CallManager)
Known Affected Releases
Symptom: One or more processes (belonging to suspect list of RisDC process throttling thread) are stuck in the suspended and are never resumed. If the parent process/thread relies on the suspended child process (eg: sftp) to timeout and return in case of delays or timeouts and does not implement timeout themselves, this can cause the parent thread/process to be stuck indefinitely as well, cause interruption to the processing that they have performing. The amount of impact depends on the number of such suspended child processes and the exact purpose for which they are used. Conditions: The issue occurs, when the server has gone through a high CPU/IO wait and the RisDC process throttling has put one or more suspect processes to hold, followed by a crash of the RisDC service. When the RisDC service starts up after that, if the high CPU/IO wait condition, is not present any more, the threads suspended before crash continues to remain suspended indefinitely.
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