[asterisk-bugs] [JIRA] (ASTERISK-26177) Deadlock while using ODBC
Leandro Dardini (JIRA)
noreply at issues.asterisk.org
Wed Jul 6 15:48:56 CDT 2016
[ https://issues.asterisk.org/jira/browse/ASTERISK-26177?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Leandro Dardini updated ASTERISK-26177:
---------------------------------------
Attachment: backtrace-threads.txt
coreshowlocks.txt
full-lock.txt
full-lock is the result of "core set debug 3" saved in /var/log/asterisk/full
coreshowlocks.txt is the result of "core show locks" run while the system was locked
backtrace-threads.txt has been produced as info on wiki.asterisk.org
> Deadlock while using ODBC
> -------------------------
>
> Key: ASTERISK-26177
> URL: https://issues.asterisk.org/jira/browse/ASTERISK-26177
> Project: Asterisk
> Issue Type: Bug
> Security Level: None
> Components: Resources/res_odbc
> Affects Versions: 13.10.0-rc1
> Environment: CentOS 6.8 64 bit with unixODBC-2.3.4-1 backported from fc23 and Oracle Mysql connector 5.3.6
> Reporter: Leandro Dardini
> Attachments: backtrace-threads.txt, coreshowlocks.txt, full-lock.txt
>
>
> When processing normal dialplan commands, including several ODBC commands, at some point, just running a simple command like "FollowMe" locks up asterisk. Running the FollowMe command with the same parameter, but without running anything before, produces no lock. The same dialplan run under asterisk 13.2.0 produces no issues.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
More information about the asterisk-bugs
mailing list