Feedback
Did this article resolve your question/issue?

   

Article

"Socket Closed" error with Casandra ODBC driver when setting TransactionMode=1 and calling SQLSetConnectAttr(SQL_ATTR_AUTOCOMMIT=SQL_AUTOCOMMIT_ON)

Information

 
Title"Socket Closed" error with Casandra ODBC driver when setting TransactionMode=1 and calling SQLSetConnectAttr(SQL_ATTR_AUTOCOMMIT=SQL_AUTOCOMMIT_ON)
URL NameSocket-Closed-error-with-Casandra-ODBC-driver-when-setting-TransactionMode-1-and-calling-SQLSetConnectAttr-SQL-ATTR-AUTOCOMMIT-SQL-AUTOCOMMIT-ON
Article Number000188401
EnvironmentProduct: Connect for ODBC Cassandra driver
Version: 08.00.0062
OS: all supported platforms
Database: Cassandra
Application: all supported applications
Question/Problem Description
The below error is received when setting TransactionMode=1 and calling SQLSetConnectAttr(SQL_ATTR_AUTOCOMMIT=SQL_AUTOCOMMIT_ON).
Steps to Reproduce
Clarifying Information
Error Message
Defect NumberDefect 69609
Enhancement Number
Cause
Resolution
Fixed in hot fix 08.00.0074. 
Refer to "Connect and Connect64 for ODBC hot fix download and install instructions" for instructions on how to download and install the hot fix.
Workaround
Notes
Last Modified Date6/1/2017 11:01 AM
Files
Disclaimer The origins of the information on this site may be internal or external to Progress Software Corporation (“Progress”). Progress Software Corporation makes all reasonable efforts to verify this information. However, the information provided is for your information only. Progress Software Corporation makes no explicit or implied claims to the validity of this information.

Any sample code provided on this site is not supported under any Progress support program or service. The sample code is provided on an "AS IS" basis. Progress makes no warranties, express or implied, and disclaims all implied warranties including, without limitation, the implied warranties of merchantability or of fitness for a particular purpose. The entire risk arising out of the use or performance of the sample code is borne by the user. In no event shall Progress, its employees, or anyone else involved in the creation, production, or delivery of the code be liable for any damages whatsoever (including, without limitation, damages for loss of business profits, business interruption, loss of business information, or other pecuniary loss) arising out of the use of or inability to use the sample code, even if Progress has been advised of the possibility of such damages.