You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2018/08/27 10:29:00 UTC

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

    [ https://issues.apache.org/jira/browse/IGNITE-9367?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16593455#comment-16593455 ] 

ASF GitHub Bot commented on IGNITE-9367:
----------------------------------------

GitHub user gromtech opened a pull request:

    https://github.com/apache/ignite/pull/4621

    IGNITE-9367 CPP: ODBC client crashes after executing query…

    ...by using a closed connection

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/gridgain/apache-ignite ignite-9367

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/ignite/pull/4621.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #4621
    
----
commit 3898e7ccb16e61039d93720e6f0865acbc9acd34
Author: Roman Guseinov <gr...@...>
Date:   2018-08-27T10:26:01Z

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

----


> 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)