Support Article
Many references to hazelcast errors are seen in the logs
SA-12238
Summary
You noticed many references to hazelcast errors in the logs.
Error Messages
[7/4/15 5:17:47:983 EDT] 0000002d BasicInvocati W com.hazelcast.spi.impl.BasicInvocation [xxx.xx.xxx.xxx]:5702 [6e7014d6a208cfdb33ef26a9d7c85b55] [3.2] No response for 120002 ms. InvocationFuture{invocation=BasicInvocation{ serviceName='hz:impl:mapService', op=GetOperation{}, partitionId=246, replicaIndex=0, tryCount=250, tryPauseMillis=500, invokeCount=1, callTimeout=60000, target=Address[xxx.xx.xxx.xxx]:5701}, done=false}
Steps to Reproduce
Not Applicable
Root Cause
The root cause of this problem is defect/misconfiguration in the operating environment. The pr_sys_statusnodes contained invalid node entries.
Resolution
This issue is resolved by truncating the pr_sys_statusnodes table and restarting the servers.
Published July 20, 2015 - Updated October 8, 2020
Have a question? Get answers now.
Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.