You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@ignite.apache.org by "Artem Shutak (JIRA)" <ji...@apache.org> on 2015/03/25 18:44:53 UTC

[jira] [Updated] (IGNITE-590) [Test] Idle check probably missbehaves in java client

     [ https://issues.apache.org/jira/browse/IGNITE-590?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Artem Shutak updated IGNITE-590:
--------------------------------
    Description: 
It looks like idle check only happens when a new connection is requested by user. So old idle connections is closed and a new one created immediately after it. We need to write tests for idle connection close behavior and fix it if needed.

see GG-3789

  was:
It looks like idle check only happens when a new connection is requested by user. So old idle connections is closed and a new one created immediately after it. We need to write tests for idle connection close behavior and fix it if needed.

see http://atlassian.gridgain.com/jira/browse/GG-3789


> [Test] Idle check probably missbehaves in java client
> -----------------------------------------------------
>
>                 Key: IGNITE-590
>                 URL: https://issues.apache.org/jira/browse/IGNITE-590
>             Project: Ignite
>          Issue Type: Bug
>            Reporter: Artem Shutak
>            Assignee: Yakov Zhdanov
>             Fix For: sprint-3
>
>
> It looks like idle check only happens when a new connection is requested by user. So old idle connections is closed and a new one created immediately after it. We need to write tests for idle connection close behavior and fix it if needed.
> see GG-3789



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)