ESP dSeries: Jobs stuck in READY state after patching to v25.1

Products

• ESP dSeries Workload Automation

Issue/Introduction

After patching ESP dSeries Workload Automation to version 25.1,  jobs may fail to execute and remain in READY status. Additionally, agents may be unable to connect to the server.

Analysis of thread dumps during the issue typically shows the heartbeatthread in a BLOCKED state.

Environment

• Product: ESP dSeries Workload Automation
• Version: 25.1

Cause

Due to huge number of inactive agents, ESP dSeries is busy with pinging/retrying agents rather than scheduling jobs.

Resolution

To resolve this issue, adjust the heartbeat interval and retry parameters to allow more overhead for the thread to recover.

Step 1: Adjust Global Agent Heartbeat Interval

1. Log in to the Desktop Client.
2. Navigate to Admin > Server Shared Parameters.
3. Go to the Internal tab and select Advanced properties.
4. Locate the parameter: Global agent heartbeat interval in minutes (0 to disable).
5. Change the value from the default (5) to 120.

Step 2: Adjust Network Retry Interval

1. In the same Server Shared Parameters dialog, navigate to the Network Retry tab.
2. Locate the parameter: Agent heartbeat ping failure retry interval (milliseconds).
3. Increase the value from 3000 to 6000.

Step 3: Apply Changes

1. Click OK to save the parameters.
2. Monitor the environment to ensure jobs transition from READY to EXECUTION and agents reconnect successfully.