[asterisk-bugs] [JIRA] (ASTERISK-26074) res_odbc: Deadlock within UnixODBC

[Ross Beer (JIRA)]

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

Ross Beer commented on ASTERISK-26074:
--------------------------------------

I'm using threading=0 with the latest unixODBC and MySQL-connector-ODBC.

Pooling has also been enabled to improve performance, however with this disabled the issue still occurs.

> res_odbc: Deadlock within UnixODBC
> ----------------------------------
>
>                 Key: ASTERISK-26074
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-26074
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Resources/res_odbc
>    Affects Versions: SVN, 13.9.1
>         Environment: CentOS 7 / Fedora Server 23
>            Reporter: Ross Beer
>         Attachments: backtrace-threads-clean.txt, core-show-locks.txt
>
>
> The appears to be a lock in the sorcery real-time identify module in the latest versions of asterisk. I have tried multiple versions of unixODBC and mysql-connector-odbc with out any luck.
> The locks cause all registrations to fail.
> The CLI is showing a couple of message types:
> [2016-05-30 16:49:43] WARNING[25214]: pjproject:0 <?>:  sip_transactio Unable to register REGISTER transaction (key exists)
> [2016-05-30 16:49:43] WARNING[25477]: pjproject:0 <?>:  sip_transactio Unable to register REGISTER transaction (key exists)
> [2016-05-30 16:49:43] WARNING[25479]: pjproject:0 <?>:  sip_transactio Unable to register REGISTER transaction (key exists)
> [2016-05-30 16:49:29] ERROR[25207]: res_pjsip.c:2899 ast_sip_create_dialog_uas: Could not create dialog with endpoint 20937*407. Object already exists (PJ_EEXISTS)



--
This message was sent by Atlassian JIRA
(v6.2#6252)