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

OperationalTimeoutException occurs and system does not respond



Executing multiple extracts from the Business Intelligence Exchange (BIX) Command Line impacts users on other nodes.

Error Messages

Caused by: com.hazelcast.core.OperationTimeoutException: QueryPartitionOperation got rejected before execution due to not starting within the operation-call-timeout of: 60000 ms. 

Caused by: com.hazelcast.core.OperationTimeoutException: CacheGetOperation got rejected before execution due to not starting within the operation-call-timeout of: 60000 ms.

Steps to Reproduce

Execute multiple extracts in parallel from the Command Line.

Root Cause

A defect or configuration issue in the operating environment.
Each BIX extraction from the Command Line starts and stops PegaEngine nstance which in turn is added and removed from the Hazelcast cluster. Executing multiple extracts in parallel means that there are multiple new members joining and leaving the cluster at the same time. As a result, the utility node performance degraded. Additionally, while the extractions are running, they are querying for the work tables used.


Perform the following local-change:

For the BIX extracts, add the below code to the prconfig.xml file which the BIX Command Line process uses to prevent Hazelcast from communicating with other nodes. <env name="identification/cluster/protocol" value="standalone" />

Additional recommendation,
  1. Apply HFix-50824.
  2. Apply HFix-46681 (to upgrade to Hazelcast 3.10 EE).

Published August 15, 2019 - Updated December 2, 2021

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