[
https://issues.apache.org/jira/browse/IGNITE-2779?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15870139#comment-15870139
]
Alexey Kuznetsov commented on IGNITE-2779:
------------------------------------------
test fails during client1 node starting
with
[18:31:29,401][SEVERE][tcp-client-disco-sock-writer-#7%client1%][TcpDiscoverySpi]
Failed to send message: TcpDiscoveryClientHeartbeatMessage
[super=TcpDiscoveryAbstractMessage [sndNodeId=null,
id=4837c874a51-62567c66-fee9-44b1-aa93-6c8721f8de3e, verifierNodeId=null,
topVer=0, pendingIdx=0, failedNodes=null, isClient=true]]
java.net.SocketException: Socket is closed
at java.net.Socket.getSendBufferSize(Socket.java:1215)
> BinaryMarshaller caches must be cleaned during client reconnect.
> ----------------------------------------------------------------
>
> Key: IGNITE-2779
> URL: https://issues.apache.org/jira/browse/IGNITE-2779
> Project: Ignite
> Issue Type: Task
> Components: cache, general
> Affects Versions: 1.5.0.final
> Reporter: Vladimir Ozerov
> Assignee: Alexey Kuznetsov
> Labels: community, important
> Fix For: 2.0
>
> Attachments: IgniteProblemTest.java
>
>
> The problem is originally reported by Vinay Sharma here:
> http://apache-ignite-users.70518.x6.nabble.com/changed-cache-configuration-and-restarted-server-nodes-Getting-exception-td3064.html#none
> *Root cause*:
> When client is reconnected to topology after full topology restart (i.e. all
> server nodes were down), it doesn't re-send binary metadata to topology. As a
> result, {{BinaryMarshaller}} exception occurs.
> *Steps to reproduce*
> Run attached code.
> *Proposed solution*
> Clean cached binary metadata during re-connect.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
