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

Posted to issues@ignite.apache.org by "Anton Kalashnikov (JIRA)" <ji...@apache.org> on 2018/08/20 13:18:00 UTC

[jira] [Updated] (IGNITE-9327) Client Nodes hangs because client reconnect not handled

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

Anton Kalashnikov updated IGNITE-9327:
--------------------------------------
    Description: 
Reproduced by IgniteCacheClientReconnectTest#testClientInForceServerModeStopsOnExchangeHistoryExhaustion

If IgniteNeedReconnectException happend we should stop the node if reconnect doesn't supported. But after https://issues.apache.org/jira/browse/IGNITE-8673 we became to ignore this case.

  was:
Reproduced by IgniteCacheClientReconnectTest#testClientInForceServerModeStopsOnExchangeHistoryExhaustion

If IgniteNeedReconnectException happend we should stop not if reconnect doens't supported. But after https://issues.apache.org/jira/browse/IGNITE-8673 we became to ignore this case.


> Client Nodes hangs because client reconnect not handled 
> --------------------------------------------------------
>
>                 Key: IGNITE-9327
>                 URL: https://issues.apache.org/jira/browse/IGNITE-9327
>             Project: Ignite
>          Issue Type: Test
>            Reporter: Anton Kalashnikov
>            Assignee: Anton Kalashnikov
>            Priority: Major
>
> Reproduced by IgniteCacheClientReconnectTest#testClientInForceServerModeStopsOnExchangeHistoryExhaustion
> If IgniteNeedReconnectException happend we should stop the node if reconnect doesn't supported. But after https://issues.apache.org/jira/browse/IGNITE-8673 we became to ignore this case.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)