[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=205947#comment-205947 ] 

Dare Awktane commented on ASTERISK-21228:
-----------------------------------------

No new calls are created. Calls in progress do not appear to close properly. I can not really confirm what happens with the calls in progress as I'm not on one of the lines and cannot create new ones. core and sip show channels output appears to remain the same. I will try your new patch shortly on both versions of asterisk. Is there anything apart from the locks that you would like me to try in case it happens again? This time I will also leave it for longer to see if the channels ever timeout.
                
> 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
>         Attachments: 1366481920-backtrace_threads.txt, 1366481920-core_show_locks.txt, 1366495718-backtrace_threads.txt, 1366495718-core_show_locks.txt, 20130425__AST-21228.patch, 20130427__AST-21228.patch, asterisk11_3-1367049271-backtrace_threads.txt, asterisk11_3-1367049271-core_show_locks.txt, 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