[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=230405#comment-230405 ] 

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

Yes, we are using:

Debian Jessie 8.4 (3.16.0-4-amd64 #1 SMP Debian 3.16.7-ckt25-1 (2016-03-06) x86_64 GNU/Linux)
libmysqlclient18 5.5.47-0+deb8u1  (from Jessie standard packages)
libmysqlclient-dev 5.5.47-0+deb8u1 (from Jessie standard packages)
mysql-common 5.5.47-0+deb8u1 (from Jessie standard packages)

UnixODBC 2.3.4 from http://www.unixodbc.org/
Mysql-connector-odbc 5.3.6 ( w - unicode version) from mysql-connector-odbc-5.3.6-linux-debian8-x86-64bit binary package from https://dev.mysql.com/downloads/connector/odbc/ 
connected to remote mysql-5.5 database with InnoDB tables

ODBC configuration as mentioned, with pooling=yes and OPTION=3

Asterisk 13.8.0 with patch mentioned in issue ASTERISK-25888 (segfaults in function can_ring_entry() of app_queue.c) no other patches applied

if you need something more please let me know.


> 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: Rusty Newton
>         Attachments: backtrace1.txt, backtrace2.txt, backtrace3.txt, bt_libmysql5_7.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)