[asterisk-bugs] [Asterisk 0010830]: IAX2: Out of idle IAX2 threads for I/O, pausing!

[noreply at bugs.digium.com]

The following issue has been RESOLVED. 
====================================================================== 
http://bugs.digium.com/view.php?id=10830 
====================================================================== 
Reported By:                callguy
Assigned To:                russell
====================================================================== 
Project:                    Asterisk
Issue ID:                   10830
Category:                   Channels/chan_iax2
Reproducibility:            always
Severity:                   crash
Priority:                   normal
Status:                     resolved
Asterisk Version:           1.4.11  
SVN Branch (only for SVN checkouts, not tarball releases): N/A  
SVN Revision (number only!):  
Disclaimer on File?:        N/A 
Request Review:              
Resolution:                 fixed
Fixed in Version:           
====================================================================== 
Date Submitted:             09-26-2007 17:54 CDT
Last Modified:              10-01-2007 11:26 CDT
====================================================================== 
Summary:                    IAX2: Out of idle IAX2 threads for I/O, pausing!
Description: 
We are seeing asterisk stop processing calls at random intervals (but
roughly once every two days or so). We see IAX peers go unreachable then
the following error on the console:

[Sep 26 18:56:18] NOTICE[10762]: chan_iax2.c:6521 socket_read: Out of idle
IAX2 threads for I/O, pausing!

Shortly after this asterisk hangs and all apps stop functioning, except
for rtp. Output of "core show locks" is attached. 

Asterisk version is 1.4.11
====================================================================== 

---------------------------------------------------------------------- 
 russell - 10-01-07 11:26  
---------------------------------------------------------------------- 
I don't think this is realted to 10406, but it is an issue that I believe I
have seen and have already fixed.  The fix is already in the 1.4 branch,
and will be in 1.4.12 when it gets released this week. 

Issue History 
Date Modified   Username       Field                    Change               
====================================================================== 
10-01-07 11:26  russell        Status                   assigned => resolved
10-01-07 11:26  russell        Resolution               open => fixed       
10-01-07 11:26  russell        Note Added: 0071263                          
======================================================================