[asterisk-bugs] [JIRA] (ASTERISK-28213) Deadlock when removing AOR after transport has done away

[Asterisk Team (JIRA)]

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

Asterisk Team commented on ASTERISK-28213:
------------------------------------------

Thanks for creating a report! The issue has entered the triage process. That means the issue will wait in this status until a Bug Marshal has an opportunity to review the issue. Once the issue has been reviewed you will receive comments regarding the next steps towards resolution.

A good first step is for you to review the [Asterisk Issue Guidelines|https://wiki.asterisk.org/wiki/display/AST/Asterisk+Issue+Guidelines] if you haven't already. The guidelines detail what is expected from an Asterisk issue report.

Then, if you are submitting a patch, please review the [Patch Contribution Process|https://wiki.asterisk.org/wiki/display/AST/Patch+Contribution+Process].

> Deadlock when removing AOR after transport has done away
> --------------------------------------------------------
>
>                 Key: ASTERISK-28213
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-28213
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Channels/chan_pjsip
>    Affects Versions: 13.24.0
>         Environment: CentOS 7.6
>            Reporter: Ross Beer
>
> A deadlock occurs on AOR removal when a transport has gone away, and a NOTIFY is being sent the endpoint. The AOR is blocked in mariadb and the second thread blocks on the first.
> The full backtrace has been sent to Geroge Joseph as it contains private information.



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