[asterisk-bugs] [JIRA] (ASTERISK-21228) Deadlock in pbx_find_extension when attempting an autoservice stop due to holding the context lock
Tilghman Lesher (JIRA)
noreply at issues.asterisk.org
Thu Apr 25 23:09:38 CDT 2013
[ https://issues.asterisk.org/jira/browse/ASTERISK-21228?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=205881#comment-205881 ]
Tilghman Lesher commented on ASTERISK-21228:
--------------------------------------------
Matt: I agree that ao2 would be a nice thing to do to the pbx core, but that is a massive undertaking. I think this patch will solve the immediate problem in short order. I was actually thinking about this solution when I wrote the patch that converted the rwlocks back to mutexes, but I abandoned that approach, because I thought that mutexes would be a simpler solution. So as it turned out, mutexes were too simple.
> 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, 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
More information about the asterisk-bugs
mailing list