Resetting heartbeat timestamps because of huge system clock jump

[Parth Bhatt]

Hello All,

Hope you all are doing well. :)

I am running hazelcast application, and I am getting below error, after putting my machine in sleep mode/log off for sometime. I am using windows machine.

Error:

[192.168.181.51]:5701 [APP] [4.2] System clock apparently jumped from 2021-06-21 14:10:28.569 to 2021-06-21 14:41:07.832 since last heartbeat (+1834263 ms) 

2021-06-21 14:41:07.855 INFO 8288 --- [cached.thread-9] c.h.i.server.tcp.TcpServerConnection : [192.168.181.51]:5701 [APP] [4.2] Connection[id=1, /127.0.0.1:5701->/127.0.0.1:5702, qualifier=null, endpoint=[127.0.0.1]:5702, alive=false, connectionType=JVM, planeIndex=-1] closed. Reason: Client heartbeat is timed out, closing connection to Connection[id=1, /127.0.0.1:5701->/127.0.0.1:5702, qualifier=null, endpoint=[127.0.0.1]:5702, alive=true, connectionType=JVM, planeIndex=-1]. Now: 

2021-06-21 14:41:07.833. LastTimePacketReceived: 2021-06-21 14:10:29.314 2021-06-21 14:41:07.915 WARN 8288 --- [cached.thread-7] c.h.i.c.impl.ClusterHeartbeatManager : [192.168.181.51]:5701 [APP] [4.2] Resetting heartbeat timestamps because of huge system clock jump! Clock-Jump: 1834263 ms, Heartbeat-Timeout: 60000 ms 

2021-06-21 14:41:08.208 WARN 8288 --- [onMonitorThread] c.h.s.i.o.impl.InvocationMonitor : [192.168.181.51]:5701 [APP] [4.2] MonitorInvocationsTask delayed 1836451 ms 

2021-06-21 14:41:08.213 WARN 8288 --- [onMonitorThread] c.h.s.i.o.impl.InvocationMonitor : [192.168.181.51]:5701 [APP] [4.2] BroadcastOperationControlTask delayed 1834623 ms 

2021-06-21 14:41:08.539 INFO 8288 --- [cached.thread-9] c.h.i.server.tcp.TcpServerConnection : [192.168.181.51]:5701 [APP] [4.2] Connection[id=2, /127.0.0.1:5701->/127.0.0.1:5703, qualifier=null, endpoint=[127.0.0.1]:5703, alive=false, connectionType=JVM, planeIndex=-1] closed. Reason: Client heartbeat is timed out, closing connection to Connection[id=2, /127.0.0.1:5701->/127.0.0.1:5703, qualifier=null, endpoint=[127.0.0.1]:5703, alive=true, connectionType=JVM, planeIndex=-1]. Now: 

2021-06-21 14:41:08.539. LastTimePacketReceived: 2021-06-21 14:10:29.949 2021-06-21 14:41:08.551 WARN 8288 --- [ached.thread-36] c.h.i.cluster.impl.MulticastService : [192.168.181.51]:5701 [APP] [4.2] Sending multicast datagram failed. Exception message saying the operation is not permitted usually means the underlying OS is not able to send packets at a given pace. It can be caused by starting several hazelcast members in parallel when the members send their join message nearly at the same time. 

Hazelcast client Configuration code:

ClientConfig clientConfig = new ClientConfig(); 

clientConfig.setClusterName("abc"); clientConfig.getNetworkConfig().addAddress("localhost"); clientConfig.getNetworkConfig().setSmartRouting(true); clientConfig.getNetworkConfig().addOutboundPortDefinition("5701-5720"); ClientConnectionStrategyConfig connectionStrategyConfig = clientConfig.getConnectionStrategyConfig(); 

ConnectionRetryConfig connectionRetryConfig = connectionStrategyConfig.getConnectionRetryConfig(); connectionRetryConfig.setInitialBackoffMillis(1000) 

 .setMaxBackoffMillis(60000) 

 .setMultiplier(2) 

 .setClusterConnectTimeoutMillis(1000) 

 .setJitter(0.2); 

  HazelcastClient hc = HazelcastClient.newHazelcastClient(clientConfig);

Please let me know what wrong configuration am I doing or why this is happening?