[Home]

Summary:ASTERISK-18249: Deadlocks when using a switch statement
Reporter:viniciusfontes (viniciusfontes)Labels:
Date Opened:2011-08-09 06:45:40Date Closed:2015-03-13 19:02:28
Priority:MajorRegression?
Status:Closed/CompleteComponents:PBX/pbx_config
Versions:SVN 1.8.5.0 Frequency of
Occurrence		Constant
Related
Issues:
is duplicated byASTERISK-21228 Deadlock in pbx_find_extension when attempting an autoservice stop due to holding the context lock
Environment:Attachments:( 0) backtrace-threads.txt
( 1) core-show-locks.txt
( 2) db.txt
Description: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@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.
Comments:By: viniciusfontes (viniciusfontes) 2011-08-09 06:47:33.049-0500

Oops, seems like JIRA don't like MySQL output. I attached the DB as a text file, db.txt.
By: viniciusfontes (viniciusfontes) 2011-08-09 09:42:17.118-0500

Still happening on latest SVN. I checked out the source using this command:

svn checkout http://svn.digium.com/svn/asterisk/branches/1.8 .