[asterisk-bugs] [Asterisk 0011862]: Possible deadlock on realtime queues.

[noreply at bugs.digium.com]

A NOTE has been added to this issue. 
====================================================================== 
http://bugs.digium.com/view.php?id=11862 
====================================================================== 
Reported By:                flujan
Assigned To:                putnopvut
====================================================================== 
Project:                    Asterisk
Issue ID:                   11862
Category:                   Applications/app_queue
Reproducibility:            always
Severity:                   block
Priority:                   normal
Status:                     assigned
Asterisk Version:           1.4.17 
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!):  
Disclaimer on File?:        N/A 
Request Review:              
====================================================================== 
Date Submitted:             01-29-2008 07:07 CST
Last Modified:              01-29-2008 13:11 CST
====================================================================== 
Summary:                    Possible deadlock on realtime queues.
Description: 
After some time working queues stop working. I try to place calls and it
works, i can even place members on a queue but the callers are not
delivered to the agents.


Recompiled asterisk with DONT_OPTIMIZE and DEBUG_THREADS and the core show
locks of the problems follows.
====================================================================== 

---------------------------------------------------------------------- 
 putnopvut - 01-29-08 13:11  
---------------------------------------------------------------------- 
norman: the "tried and failed to get lock" messages indicate that a trylock
failed. I've seen some cases (issue http://bugs.digium.com/view.php?id=11712 for
instance) where there wasn't
an obvious deadlock like there is here, but the number of "tried and failed
to get loock" messages for some of the threads numbered in the millions,
indicating there was some sort of loop that could not progress due to its
inability to grab a lock. Most of the time, though, the tried and failed to
get lock messages do not indicate a deeper problem, since they are expected
to fail every now and again. 

Issue History 
Date Modified   Username       Field                    Change               
====================================================================== 
01-29-08 13:11  putnopvut      Note Added: 0081352                          
======================================================================