Cisco Bug: CSCuj22069 - 150ksetup:Batch action taking long time to start processing
Apr 15, 2014
- Cisco Prime Collaboration
- Cisco Prime Collaboration 10.0
Known Affected Releases
Symptom: Batch project should not update the schedule status when we are schedule the batch projects. Conditions: I have observed a racing condition between two threads(Alarm clock and daemon thread), where daemon thread checks if there are any more events to process & before it acquires the lock (and gets into wait state), alarm clock set() acquires the semaphore object lock and notifies the thread. As soon as lock is available for the run(), the daemon thread is put into indefinite wait state. Though there are new events to process, as the daemon thread is put to indefinite wait state, it hangs there forever.
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