[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 15:53 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 15:53  
---------------------------------------------------------------------- 
So, the biggest thing I have noticed in your patch is that the
server_instance objects aren't getting free'd anywhere.  It's also not
clear where that should go, as there are pointers to it being stored in
various places ... I'm thinking that some reference counting may be in
order here.  I'll look into it.

Also, what was the inspiration for moving the lock to inside the server
instance instead of the sip_socket obj?

Basically, any information that you can provide that explains your changes
would be really helpful. 

Issue History 
Date Modified   Username       Field                    Change               
====================================================================== 
03-04-08 15:53  russell        Note Added: 0083371                          
======================================================================