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

[Joshua C. Colp (JIRA)]

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

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

[~awktane] Glad to hear that!

> 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, PBX/pbx_realtime
>    Affects Versions: 1.8.20.1, 1.8.21.0, 11.2.1, 11.3.0, 13.18.4
>         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, 1367129605-backtrace_threads.txt, 1367129605-core_show_locks.txt, 1367187707-backtrace_threads.txt, 1367187707-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 was sent by Atlassian JIRA
(v6.2#6252)