[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:                putnopvut
====================================================================== 
Project:                    Asterisk
Issue ID:                   11181
Category:                   Core/ManagerInterface
Reproducibility:            always
Severity:                   major
Priority:                   normal
Status:                     feedback
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:              04-14-2008 13:46 CDT
====================================================================== 
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.
======================================================================
Relationships       ID      Summary
----------------------------------------------------------------------
related to          0011730 Multiple deadlock / show channels freez...
====================================================================== 

---------------------------------------------------------------------- 
 acunningham - 04-14-08 13:46  
---------------------------------------------------------------------- 
No, the system owner decided to downgrade to 1.2.27 rather than wait for
the problem to occur again. I will let you know if we manage to get it. 

Issue History 
Date Modified   Username       Field                    Change               
====================================================================== 
04-14-08 13:46  acunningham    Note Added: 0085474                          
======================================================================