[asterisk-bugs] [JIRA] (ASTERISK-26177) func_odbc: Database handle is kept when it should be released

[Alexei Gradinari (JIRA)]

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

Alexei Gradinari commented on ASTERISK-26177:
---------------------------------------------

But in case of func_odbc single connection we shouldn't release it because we can get incorrect value executing LAST_INSERTED_ID.
Maybe Leonardo did not pay attention to CHANGES about func_odbc and res_odbc and keep the default settings for
single_db_connection = yes
max_connections =1
Of course in this case func_odbc holds 1 connection and other threads wait for releasing it.

Maybe we should disable single_db_connection by default?


> func_odbc: Database handle is kept when it should be released
> -------------------------------------------------------------
>
>                 Key: ASTERISK-26177
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-26177
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Functions/func_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)