[asterisk-bugs] [JIRA] (ASTERISK-26177) Deadlock while using ODBC

Asterisk Team (JIRA) noreply at issues.asterisk.org
Wed Jul 6 15:44:56 CDT 2016


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

Asterisk Team commented on ASTERISK-26177:
------------------------------------------

Thanks for creating a report! The issue has entered the triage process. That means the issue will wait in this status until a Bug Marshal has an opportunity to review the issue. Once the issue has been reviewed you will receive comments regarding the next steps towards resolution.

A good first step is for you to review the [Asterisk Issue Guidelines|https://wiki.asterisk.org/wiki/display/AST/Asterisk+Issue+Guidelines] if you haven't already. The guidelines detail what is expected from an Asterisk issue report.

Then, if you are submitting a patch, please review the [Patch Contribution Process|https://wiki.asterisk.org/wiki/display/AST/Patch+Contribution+Process].

> 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
>
> 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