You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Taras Ledkov (JIRA)" <ji...@apache.org> on 2018/03/22 11:24:00 UTC
[jira] [Commented] (IGNITE-7343) Add guard to prevent concurrent
usage the JDBC thin connection
[ https://issues.apache.org/jira/browse/IGNITE-7343?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16409391#comment-16409391 ]
Taras Ledkov commented on IGNITE-7343:
--------------------------------------
[~vozerov], Thank a lot. Reconnect wasn't handled properly after merge with master.
Fixed. JDBC tests are OK.
> Add guard to prevent concurrent usage the JDBC thin connection
> --------------------------------------------------------------
>
> Key: IGNITE-7343
> URL: https://issues.apache.org/jira/browse/IGNITE-7343
> Project: Ignite
> Issue Type: Task
> Components: jdbc
> Affects Versions: 2.3
> Reporter: Taras Ledkov
> Assignee: Taras Ledkov
> Priority: Major
> Fix For: 2.5
>
>
> I propose to add multi-thread guard into {{JdbcThinTcpIo#sendRequest}} method to diagnostic concurrency usage of the Ignite JDBC connection.
> The related ticket: IGNITE-7335
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)