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

[Joshua C. Colp (JIRA)]

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

Joshua C. Colp commented on ASTERISK-28213:
-------------------------------------------

I've marked this down to Minor as the deadlock itself is from the database, and the threads that pile up are a result of that. There is a possible improvement in that we could make it a bit smarter on that, so the threads don't pile up but if the database itself blocked this would still cause potential ripples.

> 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
>            Severity: Minor
>
> 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)