Skip to main content

This content has been archived and is no longer being updated. Links may not function; however, this content may be relevant to outdated versions of the product.

Support Article

java.util.concurrent.CancellationException: Task was cancelled



CancellationException is generated in the logs.

Error Messages

java.util.concurrent.CancellationException: Task was cancelled.

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.


Perform the following local-change:
  1. Truncate the pr_sys_statusnodes table.
  2. Clear the cache on all nodes (PegaAppTier and PegaUtilTier).
  3. Restart all the nodes.
Alternatively, update to Pega 7.3.1 and later versions.

Published September 27, 2018 - Updated October 8, 2020

Was this useful?

0% found this useful

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best.

Pega Community has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice
Contact us