[asterisk-bugs] [Asterisk 0011080]: SIP channel stops processing calls, but no apparent deadlock

[noreply at bugs.digium.com]

A NOTE has been added to this issue. 
====================================================================== 
http://bugs.digium.com/view.php?id=11080 
====================================================================== 
Reported By:                callguy
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   11080
Category:                   Channels/chan_sip/General
Reproducibility:            always
Severity:                   block
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:             10-24-2007 15:58 CDT
Last Modified:              10-29-2007 11:10 CDT
====================================================================== 
Summary:                    SIP channel stops processing calls, but no apparent
deadlock
Description: 
Approximately once per week we are seeing asterisk stop processing SIP
calls. The behavior is the same as a deadlock, but core show locks does not
show any evidence that there is a deadlock. 

The only way to resolve is to restart asterisk. 

output of:
core show locks
info thread
thread apply all bt

from the running process is attached.
====================================================================== 

---------------------------------------------------------------------- 
 callguy - 10-29-07 11:10  
---------------------------------------------------------------------- 
We just experienced the same issue again. One item to note in this case, it
did not happen while the server was under any particular amount of load,
though we still don't know what sequence reproduces it.

For the GDB output if you look at the details for thread
http://bugs.digium.com/view.php?id=17 it looks
identical to the errant thread from our previous output. 

Issue History 
Date Modified   Username       Field                    Change               
====================================================================== 
10-29-07 11:10  callguy        Note Added: 0072645                          
======================================================================