com.hazelcast.core.OperationTimeoutException: No response for 120000 ms
Hi Team,
We found below exception in Stack Trace.
Type java.util.concurrent.ExecutionException
Message com.hazelcast.core.OperationTimeoutException: No response for 120000 ms. Aborting invocation! BasicInvocationFuture{invocation=BasicInvocation{ serviceName='hz:core:clusterService', op=Operation{serviceName='hz:core:clusterService', callId=333292, invocationTime=1494451469329, waitTimeout=-1, callTimeout=60000}, partitionId=-1, replicaIndex=0, tryCount=1, tryPauseMillis=500, invokeCount=1, callTimeout=60000, target=Address[ Proprietary information hidden
I found related issue(https://pdn.pega.com/support-articles/hazelcast-operationtimeoutexception-no-response-120000-ms) and provided hot fix for this version 7.1.7.
We are using Version : V7.1.9 Please let us know how to resolve this issue.
Thanks In Advance.
Vishnu
Pegasystems Inc.
AU
Hello Vishnu,
We are using Hazlecast 3.4.1 post PRPC v7.1.8 and ideally this shouldn't be appearing. Are you able to see this consistently? Can you provide your topology with all the details about the nodes (like indexing, agents) whether they are on a same system so on.
Regards,
Basavaraj
CAPGEMINI
IN
Hi Basavaraj,
We found this exception triggered on 2 day's. Currently this exception is not getting triggered.
We are running our application on 2 nodes. which agents I need to check.
Regards,
Vishnu
Pegasystems Inc.
AU
Hi Vishnu,
I doesn't mean to check you any agent in specific, wanted to check the topology and if you use any specific node which is dedicated to run all the agents. If this is an intermittent issue, you will have to check internally if there were any network issues/firewall between the two nodes which is causing the disconnect between the 2 nodes.
Also check the SA-16675 on PDN if it helps
Regards,
Basavaraj