[jira] [Commented] (IGNITE-974) Discovery issue

["Dev Lakhani (JIRA)" <ji...@apache.org>]

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

Dev Lakhani commented on IGNITE-974:
------------------------------------

I've experiencing this too, I think part of the problem is that the message is a bit inaccurate. For example:

{code:title=TcpDiscoverySpi.java#L1403|borderStyle=solid}
 catch (IOException | IgniteCheckedException e) {
            if (X.hasCause(e, SocketTimeoutException.class))
                LT.warn(log, null, "Timed out waiting for message to be read (most probably, the reason is " +
                    "in long GC pauses on remote node) [curTimeout=" + timeout + ']');

            throw e;
        }
{code}

In my case the exception e is class: org.apache.ignite.IgniteCheckedException: Failed to deserialize object with given class loader: java.net.URLClassloader. It has nothing to do with GC pauses so maybe the underlying exception needs to be logged better.

> Discovery issue
> ---------------
>
>                 Key: IGNITE-974
>                 URL: https://issues.apache.org/jira/browse/IGNITE-974
>             Project: Ignite
>          Issue Type: Bug
>            Reporter: Pavel Konstantinov
>            Assignee: Semen Boikov
>            Priority: Blocker
>             Fix For: ignite-1.4
>
>
> I'm started tester with load and got in node console many messages like this:
> {code}
> 16:04:42,396][WARNING][tcp-disco-msg-worker-#5%tester][TcpDiscoverySpi] Timed out waiting for message to be read (most probably, the reason is in long GC pauses on remote node. Current timeout: 400.
> {code}



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