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

Posted to issues@ignite.apache.org by "Alexey Goncharuk (JIRA)" <ji...@apache.org> on 2018/10/11 10:00:00 UTC

[jira] [Updated] (IGNITE-9834) ClientImpl shouldn't fail JVM with 130 error code after node validation errors

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

Alexey Goncharuk updated IGNITE-9834:
-------------------------------------
    Fix Version/s: 2.8

> ClientImpl shouldn't fail JVM with 130 error code after node validation errors
> ------------------------------------------------------------------------------
>
>                 Key: IGNITE-9834
>                 URL: https://issues.apache.org/jira/browse/IGNITE-9834
>             Project: Ignite
>          Issue Type: Bug
>            Reporter: Alexey Platonov
>            Assignee: Alexey Platonov
>            Priority: Major
>              Labels: MakeTeamcityGreenAgain
>             Fix For: 2.8
>
>
> In the current number of Ignite if client (tcp-client-disco-msg-worker) receive validation error message represented by TcpDiscoveryCheckFailedMessage then client fail with 130 error code. Semantically such behavior is invalid. Client must cancel own work in normal order.



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