Why Does Unexpected Process Behavior Occur in a Cluster Server Environment?
Symptoms
Occasionally, one of these errors occurs:
- Tasks are duplicated.
- An activity is paused, but the process instance continues to run.
- After process migration, process instances fail to return to the specified activity.
Prerequisites
- AgilePoint NX OnPremises v7.0 or higher in a Cluster Server enviornment.
Cause
The built-in Cluster Server Manager (CSM) component is responsible for performing failover for running processes when an AgilePoint Server node stops. The heartbeat feature continuously monitors all AgilePoint nodes.
In certain cases, such as when the AgilePoint Server experiences overload or high network traffic, an AgilePoint Server node may not respond to the heartbeat signal for few seconds. This can mistakenly trigger the failover mechanism on another AgilePoint Server node, and disruptions to the integrity and consistency of running process instances may occur. As a result, some processes can exhibit unexpected behavior.
Resolution
Dedicate the CSM component in your environment as a separate Windows service.
To request the CSM component installation package and deployment procedures, contact AgilePoint Support.