[IGNITE-9367] CPP: ODBC client crashes after executing query with closed connection

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.6
• Fix Version/s: 2.7
• Component/s: platforms
• Labels: cpp

Environment

Ubuntu 16.04

• Assignee: Roman Guseinov
• Reporter: Roman Guseinov
• Created: 24/Aug/18 08:12
• Updated: 04/Oct/18 09:47
• Resolved: 28/Aug/18 11:42

Description

This scenario should not lead an application crash. It seems we should throw an exception like "Connection is closed" instead.

Thread dump:

Thread #1 [odbc-crash-repr] 18020 [core: 0] (Suspended : Signal : SIGSEGV:Segmentation fault)	
ignite::odbc::Connection::TryRestoreConnection() at connection.cpp:628 0x454264	
ignite::odbc::Connection::EnsureConnected() at connection.cpp:607 0x4549cd	
ignite::odbc::Connection::SyncMessage<ignite::odbc::QueryExecuteRequest, ignite::odbc::QueryExecuteResponse>() at connection.h:168 0x45c705	
ignite::odbc::query::DataQuery::MakeRequestExecute() at data_query.cpp:217 0x45c705	
ignite::odbc::Statement::InternalExecuteSqlQuery() at statement.cpp:629 0x42d32e	
ignite::odbc::Statement::InternalExecuteSqlQuery() at statement.cpp:586 0x42d499	
ignite::odbc::Statement::ExecuteSqlQuery() at statement.cpp:576 0x42d4c1	
ignite::SQLExecDirect() at odbc.cpp:395 0x42614c	
GetDataWithOdbc() at odbc-crash-reproducer.cpp:151 0x40898a	
QueryData() at odbc-crash-reproducer.cpp:172 0x408af2	
<...more frames...>

Reproducer is attached.

Issue Links

• links to: GitHub Pull Request #4621