Version

Argent Job Scheduler 10.0A-1603-A and earlier

Date

Monday, 1 August 2016

Summary

Addressed the issue that Argent Job Scheduler Primary Server gets hung when the Argent Job Scheduler backup Node goes offline

Technical Background

Argent Job Scheduler Backup Node updates a heartbeat file in a network shared path to notify the Primary Engine about its service status

This path (Failure-proof Path Of Backup) and the interval at which the path is updated (Service Status Update Frequency) are configured as shown in the figure below

Click For Full Size

Argent Job Scheduler Main Server checks for the updated heartbeat file from Backup Node at an interval specified in ‘Service Status Checking Frequency’

If Failure-proof Path Of Backup is configured in the Backup Node, Primary Server gets hung when the Argent Job Scheduler backup Node goes offline

The shared path is accessed using Microsoft APIs, which goes unresponsive when the server is inaccessible, which in turn leads the Argent Job Scheduler main process to be unresponsive and Argent Job Scheduler Service restarts

This issue has been addressed by adding bullet proof to check if the shared path server is online before checking if the file has been updated by the Backup Node

Resolution

Upgrade to Argent Job Scheduler 10.0A-1607-A or later