[asterisk-bugs] [JIRA] (ASTERISK-18249) Deadlocks when using a switch statement
Joshua Colp (JIRA)
noreply at issues.asterisk.org
Fri Mar 13 19:02:34 CDT 2015
[ https://issues.asterisk.org/jira/browse/ASTERISK-18249?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Joshua Colp closed ASTERISK-18249.
----------------------------------
Resolution: Duplicate
> Deadlocks when using a switch statement
> ---------------------------------------
>
> Key: ASTERISK-18249
> URL: https://issues.asterisk.org/jira/browse/ASTERISK-18249
> Project: Asterisk
> Issue Type: Bug
> Security Level: None
> Components: PBX/pbx_config
> Affects Versions: SVN, 1.8.5.0
> Reporter: viniciusfontes
> Attachments: backtrace-threads.txt, core-show-locks.txt, db.txt
>
>
> I found out that Asterisk deadlocks within minutes if we have a switch statement on extensions.conf. We have to use that because some extensions are stored on realtime.
> Here's the extensions.conf snippet:
> [interno]
> switch => Realtime/conferencia at extensions
> extconfig.conf is as follows:
> [settings]
> extensions => mysql,general,extensions
> And res_mysql.conf:
> [general]
> dbhost = 127.0.0.1
> dbname = gerenciador
> dbuser = root
> dbpass = mysuperfunpassword
> dbport = 3306
> Finally, the DB itself:
> mysql> select * from extensions;
> +----+-------------+-------+----------+--------+----------+
> | id | context | exten | priority | app | appdata |
> +----+-------------+-------+----------+--------+----------+
> | 17 | conferencia | 8091 | 1 | MeetMe | ${EXTEN} |
> | 18 | conferencia | 8092 | 1 | MeetMe | ${EXTEN} |
> | 16 | conferencia | 8090 | 1 | MeetMe | ${EXTEN} |
> +----+-------------+-------+----------+--------+----------+
> Backtrace and output of 'core show locks' is attached.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
More information about the asterisk-bugs
mailing list