[asterisk-bugs] [Asterisk 0019253]: Random crash with RES_ODBC related to SQLSetConnectAttr().

[Asterisk Bug Tracker]

A NOTE has been added to this issue. 
====================================================================== 
https://issues.asterisk.org/view.php?id=19253 
====================================================================== 
Reported By:                seadweller
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   19253
Category:                   Resources/res_odbc
Reproducibility:            random
Severity:                   crash
Priority:                   normal
Status:                     feedback
Asterisk Version:           1.6.2.18 
JIRA:                        
Regression:                 No 
Reviewboard Link:            
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!):  
Request Review:              
====================================================================== 
Date Submitted:             2011-05-09 09:00 CDT
Last Modified:              2011-05-17 09:21 CDT
====================================================================== 
Summary:                    Random crash with RES_ODBC related to
SQLSetConnectAttr().
Description: 
Platform information:

CentOS 5.6
Asterisk 1.6.2.18
MySQL 5.5.11
MySQL ODBC Connector 5.1.8 or 3.5.1
unixODBC 2.2.11 (Current CentOS Release)

Received a couple random crashes relating to ODBC access.  Thought it was
a MySQL Connector issue, as I was initially using 3.5.1, so I upgraded to
5.1.8 and the issue still popped up.

I don't believe this bug is related to
https://issues.asterisk.org/view.php?id=19250 which I posted yesterday. 
Connection pooling is not turned on when this happens (the workaround for
https://issues.asterisk.org/view.php?id=19250)... but because of the other bug,
it's hard to test whether it has
an effect or not.

Not sure if unixODBC 2.2.11 is too old for Asterisk or not?  Though since
it seems to be calling SQLSetConnectAttr() in regards to
SQL_ATTR_AUTOCOMMIT which is a valid flag in 2.2.11... I don't think this
is the issue either.
====================================================================== 

---------------------------------------------------------------------- 
 (0135045) seadweller (reporter) - 2011-05-17 09:21
 https://issues.asterisk.org/view.php?id=19253#c135045 
---------------------------------------------------------------------- 
Have been testing with a non-optimized Asterisk and the 19250 patch using
connection pooling.  Ran over half a million calls through it and no
SEGFAULT.

Not sure if it would re-appear if pooling was disabled, but at this
point... I think this issue can be closed. 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2011-05-17 09:21 seadweller     Note Added: 0135045                          
======================================================================