[
https://issues.apache.org/jira/browse/IGNITE-998?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14580439#comment-14580439
]
Semen Boikov commented on IGNITE-998:
-------------------------------------
Initial issue is fixed, but there are still scenario when pending messages are
not handled properly, see test testClientReconnectTopologyChange2.
> Error in client reconnect handling
> ----------------------------------
>
> Key: IGNITE-998
> URL: https://issues.apache.org/jira/browse/IGNITE-998
> Project: Ignite
> Issue Type: Bug
> Components: general
> Reporter: Semen Boikov
> Assignee: Semen Boikov
> Priority: Critical
> Fix For: sprint-6
>
>
> Added test
> TcpClientDiscoverySpiSelfTest.testClientReconnectOneServerOneClient provoking
> reconnect on network error.
> In debugger see that in ServerImpl.processClientReconnectMessage server sees
> that collection of pending events is null and rejects reconnect, but actually
> it is valid scenario when there are no pending events.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
