[asterisk-bugs] [Asterisk 0011181]: Manager API hangs on "Command: show channels"

[noreply at bugs.digium.com]

A NOTE has been added to this issue. 
====================================================================== 
http://bugs.digium.com/view.php?id=11181 
====================================================================== 
Reported By:                acunningham
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   11181
Category:                   Core/ManagerInterface
Reproducibility:            always
Severity:                   major
Priority:                   normal
Status:                     new
Asterisk Version:           1.4.13  
SVN Branch (only for SVN checkouts, not tarball releases): N/A  
SVN Revision (number only!):  
Disclaimer on File?:        N/A 
Request Review:              
====================================================================== 
Date Submitted:             11-07-2007 07:02 CST
Last Modified:              01-15-2008 13:39 CST
====================================================================== 
Summary:                    Manager API hangs on "Command: show channels"
Description: 
If a client connects to the manager API, and does the following:

Action: Command
Command: show channels

That manager API session hangs indefinitely. Both "show channels" and
"show channels concise" are affected, but other commands such as "core set
verbose 9" are not. This affects both Asterisk 1.4.11 and 1.4.13, and
possibly other versions as well.
====================================================================== 

---------------------------------------------------------------------- 
 putnopvut - 01-15-08 13:39  
---------------------------------------------------------------------- 
The core show locks output you have provided shows the same deadlock
experienced in issue http://bugs.digium.com/view.php?id=11730. I uploaded a
patch there (called 11730.patch).
Please try using that and see if that fixes the issue. 

Issue History 
Date Modified   Username       Field                    Change               
====================================================================== 
01-15-08 13:39  putnopvut      Note Added: 0076989                          
======================================================================