[asterisk-bugs] [JIRA] (ASTERISK-21228) Deadlock in pbx_find_extension when attempting an autoservice stop due to holding the context lock

[Dare Awktane (JIRA)]

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

Dare Awktane edited comment on ASTERISK-21228 at 4/25/13 10:32 PM:
-------------------------------------------------------------------

Wanted to add something I've noticed in the messages log when it happens. I believe this is likely caused by the deadlock rather than the cause of but still worth mentioning. These messages get spammed for a while until sip show channels shows nothing.

[Apr 19 08:20:28] WARNING[30995][C-000002ca] res_rtp_asterisk.c: RTP Read too short
[Apr 19 08:20:41] WARNING[31021][C-000002cb] res_rtp_asterisk.c: RTP Read too short

(confirmed that this is because of the issue not the cause of the issue)
                
      was (Author: awktane):
    Wanted to add something I've noticed in the messages log when it happens. I believe this is likely caused by the deadlock rather than the cause of but still worth mentioning. These messages get spammed for a while until sip show channels shows nothing.

[Apr 19 08:20:28] WARNING[30995][C-000002ca] res_rtp_asterisk.c: RTP Read too short
[Apr 19 08:20:41] WARNING[31021][C-000002cb] res_rtp_asterisk.c: RTP Read too short

                  
> Deadlock in pbx_find_extension when attempting an autoservice stop due to holding the context lock
> --------------------------------------------------------------------------------------------------
>
>                 Key: ASTERISK-21228
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-21228
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Core/PBX
>    Affects Versions: 1.8.20.1, 1.8.21.0, 11.2.1, 11.3.0
>         Environment: Linux 3.2.0-38-generic #61-Ubuntu SMP x86_64 x86_64 x86_64 GNU/Linux
>            Reporter: Dare Awktane
>            Severity: Critical
>         Attachments: 1366481920-backtrace_threads.txt, 1366481920-core_show_locks.txt, 1366495718-backtrace_threads.txt, 1366495718-core_show_locks.txt, 20130425__AST-21228.patch, backtrace-threads.txt, core-show-locks.txt
>
>
> Due to the way locks are maintained it appears as though our realtime switch calls in our extensions.conf, which are also stored in the database via odbc, are causing a conflict. We have 5500 contexts any of which can be called at any time as each one exists to maintain separation between our customers.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.asterisk.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira