Support Article
java.util.concurrent.CancellationException: Task was cancelled
SA-63149
Summary
CancellationException is generated in the logs.
Error Messages
java.util.concurrent.CancellationException: Task was cancelled.
at com.google.common.util.concurrent.AbstractFuture.cancellationExceptionWithCause(AbstractFuture.java:392)
at com.google.common.util.concurrent.AbstractFuture$Sync.getValue(AbstractFuture.java:306)
at com.google.common.util.concurrent.AbstractFuture$Sync.get(AbstractFuture.java:272)
at com.google.common.util.concurrent.AbstractFuture.get(AbstractFuture.java:96)
Steps to Reproduce
Not Applicable
Root Cause
The unique identifier for the node changed unexpectedly. One of nodes in the cluster was terminated. Hazelcast changed the unique identifier as part of its cluster Merge process or Split Brain resolution process.
The request hit Node 1 and attempted to connect to Nodes 2 and 3. However, it was unable to. Node 1 was formed on a cluster since Hazelcast was configured to connect indefinitely and continued to search for Nodes 2 and 3. These nodes were not found and the system of records was updated. Hence, the exception was generated.
Resolution
Perform the following local-change:
- Truncate the pr_sys_statusnodes table.
- Clear the cache on all nodes (PegaAppTier and PegaUtilTier).
- Restart all the nodes.
Published September 27, 2018 - 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.