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

Taras Ledkov commented on IGNITE-7343:
--------------------------------------

[~vozerov]
About *p.3* the {{ownThread}} is set on the enter to the method {{sendRequest}} 
and reset to *null* en exit from the method.
So, I guess connection pools will work properly.

> 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
>             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
(v6.4.14#64029)

Reply via email to