[asterisk-bugs] [Asterisk 0011972]: tls transport often causes asterisk to lock

[noreply at bugs.digium.com]

A NOTE has been added to this issue. 
====================================================================== 
http://bugs.digium.com/view.php?id=11972 
====================================================================== 
Reported By:                pj
Assigned To:                jamesgolovich
====================================================================== 
Project:                    Asterisk
Issue ID:                   11972
Category:                   Channels/chan_sip/General
Reproducibility:            random
Severity:                   block
Priority:                   normal
Status:                     assigned
Asterisk Version:           SVN 
SVN Branch (only for SVN checkouts, not tarball releases):  trunk 
SVN Revision (number only!): 103313 
Disclaimer on File?:        N/A 
Request Review:              
====================================================================== 
Date Submitted:             02-11-2008 11:04 CST
Last Modified:              03-04-2008 19:23 CST
====================================================================== 
Summary:                    tls transport often causes asterisk to lock
Description: 
when asterisk is locked, no call or registration is processed,
this happened several times today and yesterday (tried several trunk
revisions)
currently haven't found thing, what causes the locking situation, 
it seems, that locking problem start appearing, after more peers start
using tls transport
my tls only peers are: asterisk trunk, asterisk beta2 and eyebeam
sofphone
+several udp clients.



====================================================================== 

---------------------------------------------------------------------- 
 russell - 03-04-08 19:23  
---------------------------------------------------------------------- 
So, the general idea with using astobj2 for this is to make sure that the
server instance won't get destroyed until it is no longer possible for it
to be referenced anywhere in the code.  So, when a pointer to the server
instance is copied into another object, (usually one with a sip_socket in
it, like sip_peer, sip_pvt, whatever), then the reference count of the
object reflects it.  Then, when that object that contains a pointer to the
server instance goes away, it decrements the reference count.  When the ref
count hits zero, the object gets free'd. 

Issue History 
Date Modified   Username       Field                    Change               
====================================================================== 
03-04-08 19:23  russell        Note Added: 0083393                          
======================================================================