[asterisk-bugs] [Asterisk 0012044]: Multiple deadlock / show channels freeze on Queues 1.4.16/17

[noreply at bugs.digium.com]

A NOTE has been added to this issue. 
====================================================================== 
http://bugs.digium.com/view.php?id=12044 
====================================================================== 
Reported By:                DougUDI
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   12044
Category:                   Channels/chan_agent
Reproducibility:            sometimes
Severity:                   crash
Priority:                   normal
Status:                     new
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:             02-21-2008 01:51 CST
Last Modified:              02-21-2008 09:04 CST
====================================================================== 
Summary:                    Multiple deadlock / show channels freeze on Queues
1.4.16/17
Description: 
I have a problem that was patched in the past and this did solve the issue
untill lately. We get calls that will get stuck in the queue and never be
passed to an agent, the Zap channel is open but the caller has hung up.
Seems like a deadlock related to queues. The original ticket 0011730 was
succefully patched, but some how this problem has started again. Show
channels has output but does not give a final channel count and afer this
command the CLI becomes unreponsive very much like the problem in ticket
0011712. When we have a call in the queue that gets stuck Asterisk will
cause load ave to get extreamly high in the ranges of 300.0. The only way
to clear this error is to restart Asterisk. I will try and recompile a
debug version of Asterisk to collect the lock info as did last time.
====================================================================== 

---------------------------------------------------------------------- 
 russell - 02-21-08 09:04  
---------------------------------------------------------------------- 
The first thing that you need to do is to update to the latest version
(1.4.18). 

Issue History 
Date Modified   Username       Field                    Change               
====================================================================== 
02-21-08 09:04  russell        Note Added: 0082729                          
======================================================================