[asterisk-bugs] [JIRA] (ASTERISK-25891) Crash using ODBC in mysql with heavy usage

[Carlos Oliva (JIRA)]

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

Carlos Oliva commented on ASTERISK-25891:
-----------------------------------------

Ross:

No, I'm not using Threading=0 but I'm using pooling in UnixODBC as recomended in upgrade.txt. Do you think Threading=0 can help?

My ODBC Config files are:

root at asterisktest:/# cat /etc/odbcinst.ini 
[MySQL]

Description = ODBC for MySQL
Driver = /usr/local/lib/mysql-connector-odbc-5.3.6/libmyodbc5a.so
Setup  = /usr/local/lib/mysql-connector-odbc-5.3.6/libmyodbc5S.so
FileUsage = 1
Pooling = Yes
root at asterisktest:/# cat /etc/odbc.ini 
[DB]
Description    = Connection to DB1
Driver         = MySQL
Database       = myDb
Server         = x.y.z.k
user           = myuser
Password       = mypass
Port           = 3306
CPTimeout      = 120

Michael:

As you suggested I tried using latest debian mysql client libraries provided by mysql (packages 5.7.11-1debian8 and with 5.6.29-1debian8 ) both with core dump result  using latest mysql-connector-odbc from mysql (BT posted as bt_libmysql_5_7.txt)

Now i'm testing with standard debian8 libmysqlclient18 (5.5.47-0+deb8u1) with latest mysql-connector-odbc (5.3.6) I'll post more feedback when I have more data

> Crash using ODBC in mysql with heavy usage
> ------------------------------------------
>
>                 Key: ASTERISK-25891
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-25891
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Resources/res_odbc
>    Affects Versions: 13.8.0
>         Environment: debian jessie 8.4 (KVM virtual machine)
>            Reporter: Carlos Oliva
>            Assignee: Carlos Oliva
>         Attachments: backtrace1.txt, backtrace2.txt, backtrace3.txt
>
>
> testing release 13.8.0 I found crashes making heavy use of ODBC with mysql. This issue seems to not happen in 13.7.2 release.
> We make a heavy usage of mysql using ODBC, dialplan functions and CEL. The isse seems to happen with 4 or 5 calls using queues, cel logging to mysql and lots of database calls in the dialplan.
>  I think maybe related to Change-Id: I37a84def5ea4ddf93868ce8105f39de078297fbf (res_odbc: Remove connection management) because it directly affects to odbc connection settings. 
> I will attach some backtraces where you can see clearly the issue is related to odbc and libmysqlclient.so.18



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