[asterisk-bugs] [JIRA] (ASTERISK-24540) Presence Causes Deadlock

[Ross Beer (JIRA)]

     [ https://issues.asterisk.org/jira/browse/ASTERISK-24540?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ross Beer updated ASTERISK-24540:
---------------------------------

    Status: Waiting for Feedback  (was: Waiting for Feedback)

I think the issue is that the issue is that the cache should be hit before looking up details in the database. For example an outgoing call when using 'type=friend' appears to do a number of database lookups for each call and registration. 

When there is heavy load, this can cause a strain on the database. This should be avoided when using real time cache, however in version 11 and 13  the cache is the last thing checked where as it should the the first.

Asterisk 1.8 does not have the same issue and therefore it would be great if we could resolve this in 11 and 13 to aid our migration to PJSIP which is the plan, however we would like to move to 13 using the existing SIP driver in the first instance.

13 should resolve a few issues experienced with 1.8 so the first hurdle would be to upgrade to 13 before moving to the very new PJSIP driver.

> Presence Causes Deadlock
> ------------------------
>
>                 Key: ASTERISK-24540
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-24540
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Channels/chan_sip/General
>    Affects Versions: 1.8.32.0, 11.14.0, 11.14.1, 13.2.0
>         Environment: CentOS 6.4, CentOS 6.5, CentOS 7
>            Reporter: Ross Beer
>            Assignee: Ross Beer
>         Attachments: backtrace-threads_21-11-2014-clean.txt, backtrace-threads-clean_server2.txt, backtrace-threads-clean.txt, lsof_24-11-2014_1158.txt, server2_additional_debug.txt, threads.txt
>
>
> We are experiencing an issue where the SIP channel driver pauses and does not allow further registrations or calls to progress.
> Looking at core dumps shows lock waits for app_dial and presence.
> Unfortunately asterisk had not been compiled with the correct settings so I will need to provide further back traces when the issue happens again, however have attached the files I have now.



--
This message was sent by Atlassian JIRA
(v6.2#6252)