Client heartbeat is timed out

304 views
Skip to first unread message

Abdülhakim Ünlü

unread,
Aug 9, 2016, 4:43:04 AM8/9/16
to Hazelcast
Hi,

After the load-test I mentioned in the below post:

https://groups.google.com/d/msg/hazelcast/rVcK3M4uO_Q/bUnTs-YJCQAJ

In hazelcast server logs, following logs are printed continuously, although the clients on that endpoint is shutdown:

WARNING: Client heartbeat is timed out , closing connection to Connection [0.0.0.0/0.0.0.0:5701 -> null], endpoint=Address[137.58.63.49]:40992, alive=false, type=JAVA_CLIENT
Aug 09, 2016 11:15:13 AM com.hazelcast.client.impl.ClientHeartbeatMonitor
WARNING: Client heartbeat is timed out , closing connection to Connection [0.0.0.0/0.0.0.0:5701 -> null], endpoint=Address[137.58.63.49]:40992, alive=false, type=JAVA_CLIENT
Aug 09, 2016 11:15:23 AM com.hazelcast.client.impl.ClientHeartbeatMonitor
WARNING: Client heartbeat is timed out , closing connection to Connection [0.0.0.0/0.0.0.0:5701 -> null], endpoint=Address[137.58.63.49]:40992, alive=false, type=JAVA_CLIENT
Aug 09, 2016 11:15:33 AM com.hazelcast.client.impl.ClientHeartbeatMonitor
WARNING: Client heartbeat is timed out , closing connection to Connection [0.0.0.0/0.0.0.0:5701 -> null], endpoint=Address[137.58.63.49]:40992, alive=false, type=JAVA_CLIENT
Aug 09, 2016 11:15:43 AM com.hazelcast.client.impl.ClientHeartbeatMonitor
WARNING: Client heartbeat is timed out , closing connection to Connection [0.0.0.0/0.0.0.0:5701 -> null], endpoint=Address[137.58.63.49]:40992, alive=false, type=JAVA_CLIENT
Aug 09, 2016 11:15:53 AM com.hazelcast.client.impl.ClientHeartbeatMonitor
WARNING: Client heartbeat is timed out , closing connection to Connection [0.0.0.0/0.0.0.0:5701 -> null], endpoint=Address[137.58.63.49]:40992, alive=false, type=JAVA_CLIENT
Aug 09, 2016 11:16:03 AM com.hazelcast.client.impl.ClientHeartbeatMonitor
WARNING: Client heartbeat is timed out , closing connection to Connection [0.0.0.0/0.0.0.0:5701 -> null], endpoint=Address[137.58.63.49]:40992, alive=false, type=JAVA_CLIENT
Aug 09, 2016 11:16:13 AM com.hazelcast.client.impl.ClientHeartbeatMonitor
WARNING: Client heartbeat is timed out , closing connection to Connection [0.0.0.0/0.0.0.0:5701 -> null], endpoint=Address[137.58.63.49]:40992, alive=false, type=JAVA_CLIENT
Aug 09, 2016 11:16:23 AM com.hazelcast.client.impl.ClientHeartbeatMonitor
WARNING: Client heartbeat is timed out , closing connection to Connection [0.0.0.0/0.0.0.0:5701 -> null], endpoint=Address[137.58.63.49]:40992, alive=false, type=JAVA_CLIENT
Aug 09, 2016 11:16:33 AM com.hazelcast.client.impl.ClientHeartbeatMonitor
WARNING: Client heartbeat is timed out , closing connection to Connection [0.0.0.0/0.0.0.0:5701 -> null], endpoint=Address[137.58.63.49]:40992, alive=false, type=JAVA_CLIENT
Aug 09, 2016 11:16:44 AM com.hazelcast.client.impl.ClientHeartbeatMonitor
WARNING: Client heartbeat is timed out , closing connection to Connection [0.0.0.0/0.0.0.0:5701 -> null], endpoint=Address[137.58.63.49]:40992, alive=false, type=JAVA_CLIENT
Aug 09, 2016 11:16:54 AM com.hazelcast.client.impl.ClientHeartbeatMonitor
WARNING: Client heartbeat is timed out , closing connection to Connection [0.0.0.0/0.0.0.0:5701 -> null], endpoint=Address[137.58.63.49]:40992, alive=false, type=JAVA_CLIENT
Aug 09, 2016 11:17:04 AM com.hazelcast.client.impl.ClientHeartbeatMonitor
WARNING: Client heartbeat is timed out , closing connection to Connection [0.0.0.0/0.0.0.0:5701 -> null], endpoint=Address[137.58.63.49]:40992, alive=false, type=JAVA_CLIENT
Aug 09, 2016 11:17:14 AM com.hazelcast.client.impl.ClientHeartbeatMonitor
WARNING: Client heartbeat is timed out , closing connection to Connection [0.0.0.0/0.0.0.0:5701 -> null], endpoint=Address[137.58.63.49]:40992, alive=false, type=JAVA_CLIENT

Peter Veentjer

unread,
Aug 11, 2016, 9:14:56 AM8/11/16
to haze...@googlegroups.com
Which hz version are you using?

Can you make a github ticket, because it smell like a bug.

--
You received this message because you are subscribed to the Google Groups "Hazelcast" group.
To unsubscribe from this group and stop receiving emails from it, send an email to hazelcast+unsubscribe@googlegroups.com.
To post to this group, send email to haze...@googlegroups.com.
Visit this group at https://groups.google.com/group/hazelcast.
To view this discussion on the web visit https://groups.google.com/d/msgid/hazelcast/a439427c-4c86-4abb-b218-37bceee8e94f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Ricardo Riveros

unread,
Aug 24, 2016, 3:12:52 PM8/24/16
to Hazelcast
Any updates on this issue. I keep seeing this in our logs as well?

Thanks

ih...@hazelcast.com

unread,
Aug 25, 2016, 3:59:46 AM8/25/16
to Hazelcast
Hello Abdülhakim,

Can you also share the logs prior to these logs. I am especially interested in the logs about socket closing:

Something similar to: Connection [" + connAddress + "] lost. Reason: 

Better yet, can you share all the logs for both client and the server. At least the logs when the heartbeat failure started?

Regards,
ihsan

dlu...@milezero.com

unread,
Aug 29, 2016, 4:51:34 AM8/29/16
to Hazelcast
we have the same issue periodically

Reply all
Reply to author
Forward
0 new messages