[asterisk-bugs] [JIRA] (ASTERISK-28423) ARI causes STASIS Deadlock

[Kevin Harwell (JIRA)]

    [ https://issues.asterisk.org/jira/browse/ASTERISK-28423?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=249546#comment-249546 ] 

Kevin Harwell commented on ASTERISK-28423:
------------------------------------------

>From what I can tell the [original patch|https://gerrit.asterisk.org/c/asterisk/+/13171] does indeed fix a deadlock that involved the "apps_registry" and "event_session" objects.

This is just a guess as I've only done a code inspection, and haven't seen a backtrace for the latest reported deadlock, but I think fixing that exposed another deadlock further "down". This time involving "app" and "event_session" objects:

Partial call stack for Thread A:
{noformat}
stasis_app_message_handler --> ao2_lock(session)
app_send
app_update --> ao2_lock(app)
__stasis_app_register
...
{noformat}
Partial call stack for Thread B:
{noformat}
stasis_app_event_allowed --> ao2_lock(app)
stasis_app_message_handler --> ao2_lock(session)
app_send
sub_channel_update_handle
...
{noformat}

> ARI causes STASIS Deadlock
> --------------------------
>
>                 Key: ASTERISK-28423
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-28423
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Resources/res_stasis
>    Affects Versions: 13.26.0, GIT
>         Environment: CentOS 7
>            Reporter: Ross Beer
>            Assignee: George Joseph
>      Target Release: 13.30.0, 16.7.0, 17.1.0
>
>
> When using WebSocket ARI connections and the connection drops multiple times, stasis deadlocks. 



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