[jira] [Commented] (IGNITE-6330) Thin clients: close query cursors on disconnect

["ASF GitHub Bot (JIRA)" <ji...@apache.org>]

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

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

GitHub user isapego opened a pull request:

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

    IGNITE-6330: Implemented closing of ODBC and JDBC cursors on client disconnect

    

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

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

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

    https://github.com/apache/ignite/pull/2646.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 #2646
    
----
commit 2b8b19b9fdfb6809014195d2f3ce21e8a359f1a0
Author: Igor Sapego <is...@gridgain.com>
Date:   2017-09-12T14:08:19Z

    IGNITE-6330: Implemented closing of ODBC and JDBC cursors on disconnect

----


> Thin clients: close query cursors on disconnect
> -----------------------------------------------
>
>                 Key: IGNITE-6330
>                 URL: https://issues.apache.org/jira/browse/IGNITE-6330
>             Project: Ignite
>          Issue Type: Bug
>          Components: jdbc, odbc
>            Reporter: Pavel Tupitsyn
>            Assignee: Igor Sapego
>             Fix For: 2.3
>
>
> {{JdbcRequestHandler}} and {{OdbcRequestHandler}} store active cursors in {{qryCursors}} map. If client connection abruptly ends, these cursors are not closed properly.
> {{SqlListenerNioListener.onDisconnected}} should call {{SqlListenerConnectionContext.onDisconnected}}, and connection context should clean up all resources there.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)