You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2017/08/18 12:29:00 UTC

[jira] [Commented] (IGNITE-5869) Unexpected timeout exception while client connected with different BinaryConfiguration compactFooter param.

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

ASF GitHub Bot commented on IGNITE-5869:
----------------------------------------

GitHub user zstan opened a pull request:

    https://github.com/apache/ignite/pull/2482

    IGNITE-5869 client hangs infinitely while binary configuration differs from server

    

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/gridgain/apache-ignite ignite-5869

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/ignite/pull/2482.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #2482
    
----
commit 4de9de484dc595e816f8024b18c2988d5bd03983
Author: Evgeny Stanilovskiy <es...@gridgain.com>
Date:   2017-08-18T12:23:42Z

    IGNITE-5869 client hangs infinitely while binary configuration differs from server

----


> Unexpected timeout exception while client connected with different BinaryConfiguration compactFooter param.
> -----------------------------------------------------------------------------------------------------------
>
>                 Key: IGNITE-5869
>                 URL: https://issues.apache.org/jira/browse/IGNITE-5869
>             Project: Ignite
>          Issue Type: Bug
>          Components: clients
>    Affects Versions: 2.0
>            Reporter: Stanilovsky Evgeny
>            Assignee: Stanilovsky Evgeny
>         Attachments: TcpClientDiscoveryMarshallerCheckSelfTest.java
>
>
> While client connecting with different from cluster BinaryConfiguration::setCompactFooter param, instead of expecting: "configuration is not equal" exception catch: Join process timed out exception.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)