[asterisk-bugs] [Asterisk 0016066]: channel.c:2711 __ast_read: Exception flag set on 'SIP/xxx', but no exception handler

[Asterisk Bug Tracker]

A NOTE has been added to this issue. 
====================================================================== 
https://issues.asterisk.org/view.php?id=16066 
====================================================================== 
Reported By:                Micc
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   16066
Category:                   Channels/General
Reproducibility:            random
Severity:                   minor
Priority:                   normal
Status:                     acknowledged
Asterisk Version:           SVN 
JIRA:                       SWP-1436 
Regression:                 No 
Reviewboard Link:            
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!):  
Request Review:              
====================================================================== 
Date Submitted:             2009-10-13 16:17 CDT
Last Modified:              2010-05-18 23:00 CDT
====================================================================== 
Summary:                    channel.c:2711 __ast_read: Exception flag set on
'SIP/xxx', but no exception handler
Description: 
I'm running asterisk 1.6.1.6 and have been seeing this problem for about a
week or two. This happens seemingly randomly and on different channels. And
when it happens it fills the logs and the CLI with these messages as fast
as it can, jumping the cpu way up, probably 100% on one core.

I will try to get a sip debug when it happens, but I wanted to at least
get this on the issue tracker in case someone already knows what it is.
====================================================================== 

---------------------------------------------------------------------- 
 (0122110) JJCinAZ (reporter) - 2010-05-18 23:00
 https://issues.asterisk.org/view.php?id=16066#c122110 
---------------------------------------------------------------------- 
This is definitely an issue.  This condition will consume all cycles on a
core and if it happens on too many cores at once, Asterisk stops
responding.  The condition is mitagated because the ast_log() call delays
the thread somewhat.  Take that log message out and this quickly kills a
server. 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2010-05-18 23:00 JJCinAZ        Note Added: 0122110                          
======================================================================