ESP dSeries Workload Automation

 View Only

 Has anyone seen a difference in the handling of File Monitor jobs or File Trigger Events with the R12 Agent?

Francis Meckevech's profile image
Francis Meckevech posted Mar 11, 2021 01:40 PM
We currently have an issue where our jobs that are active as a result of the triggering of a file trigger Event go to READY state and never come out.  The other extenuating circumstance is that all of the components, other than the DE application server are in the cloud, e.g. Agents are in the Azure cloud and the NAS is also in the cloud.  We have verified that everything seems to be working as expected other than actually processing the received files.  We have tried various AGENTPARM parameters, e.g. filemonplugin.runexternal=true or filemonplugin.dispatcher.queue_size=2 that sometime get us out but we still need to recycle the Agent and resubmit the jobs stuck in ready.  Yesterday we actually back leveled one of the Agents to R11.5 and we have not had an issue since that time.  
All of this being said the issue only seems to appear, and not clear itself out, if there are 10+ jobs processing on the Agent all waiting for service but stuck in ready.  We sometimes see some slowness in processing multiple jobs but only when we hit a spike on the Agent do we see the stuck in READY.
I can see many jobs moving through the older R11 Agents without issue.
Has anyone else seen this?
Let me know your thoughts
BTW:  All of our CA Workload Automation DE are at the newest release/patch level.