[ https://issues.apache.org/jira/browse/IGNITE-9367?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16594844#comment-16594844
]
Igor Sapego commented on IGNITE-9367:
-------------------------------------
[~guseinov] tests pass. Everything looks OK now.
> CPP: ODBC client crashes after executing query with closed connection
> ---------------------------------------------------------------------
>
> Key: IGNITE-9367
> URL: https://issues.apache.org/jira/browse/IGNITE-9367
> Project: Ignite
> Issue Type: Bug
> Components: platforms
> Affects Versions: 2.6
> Environment: Ubuntu 16.04
> Reporter: Roman Guseinov
> Assignee: Roman Guseinov
> Priority: Major
> Labels: cpp
> Attachments: odbc-crash-reproducer.cpp, server-config.xml
>
>
> This scenario should not lead an application crash. It seems we should throw an exception
like "Connection is closed" instead.
> Thread dump:
> {code:java}
> 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...>
> {code}
> Reproducer is attached.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
|