WOBTRIG RETRYDELAY operand is not honored

Products

• ESP Workload Automation

Issue/Introduction

  Using RETRYCOUNT(10) RETRYDELAY(1) in a WOBTRIG event, the RetryDelay(1) is not being honored;
   It is delaying a full 5 minutes and not 1 minute.

 

Environment

Component : ESP WORKLOAD AUTOMATION
Release : 12.0

Cause

Using the WOBDELAY/RETRYDELAY parameter to specify a delay before the WOBRETRY/RETRYCOUNT retry attempt of WOBTRIG monitor, after it fails on the agent side. The WOBTRIG parameters allow ESP to automatically retry an initialization of the WOBTRIG monitor on the agent side when the monitor fails, for example, after a connectivity issue with a network folder. 

RETRYCOUNT(10) RETRYDELAY(1) = On failure delay 1 minute then retry scan 10 times.

If the Agent has been configured to use the FileMonplugin parameters below the agent behavior is Agent will retry the scan 5 times with a 60000ms/1 min delay for each scan to be retried, before sending a scan failed AFM back to ESP. 

filemonplugin.scan.retries=5
# sleep=60000 should be 1 minute apart
filemonplugin.scan.retries.sleep=60000

This is where the 5 minutes delay is coming from, 5 retries every minute. Once the 5th retry is attempted and agent sets scan failed, it will send the AFM back to ESP. ESP will then RETRY scan again, up to 10 times this example. ESP and Agent are working at the same thing. However without RETRYCOUNT when the 5th retry of the agent fails the WOBTRIG event goes to scan failed and does not reset. It has to be manually edited for the WOBTRIG event to be reset.  

 

Resolution

You can use these parameters together, setting the values to a more desired retry and delay time on the agent. Or remove the FileMonPlugin if you do not want the agent to retry the scan and let ESP initiate a retry.

Additional Information

WOBRETRY

WOBDELAY