ALERT: Some images may not load properly within the Knowledge Base Article. If you see a broken image, please right-click and select 'Open image in a new tab'. We apologize for this inconvenience.

WA DE (dSeries): File trigger event experiencing delays

book

Article ID: 199282

calendar_today

Updated On:

Products

CA Workload Automation DE - Business Agents (dSeries) CA Workload Automation DE DSERIES- SERVER CA Workload Automation DE - System Agent (dSeries) CA Workload Automation DE - Scheduler (dSeries)

Issue/Introduction

File trigger event monitors for file creation.  The WA Agent runs a job that constantly monitors for files in a specified location. In some cases, the file trigger may stop after few event triggers.

Cause

The WA Agent constantly monitors for files.  If searching for wildcards, e.g. AB*.txt, *.123, then it is possible that some OS and filesystems may experience latency. 

Environment

Release : 11.3/11.4/11.5/R12

Component : CA WORKLOAD AUTOMATION AGENT

Resolution

Increase the WA Agent polling

filemonplugin.scan.retries.sleep=30000
filemonplugin.sleepperiod=60000


The first property will try to scan every 30 seconds, and second will provide a sleep of one minute/60 seconds.  Add the above in the agentparm.txt and restart the agent.  

Additional Information

For dSereis (DE), consider the following:

1.  Uncheck Recursive box in the File trigger event.  Recursive is mainly used if searching for files in sub-directories.

2.  Remove 'Do Not Trigger if Active' and from application properties.   The 'Do Not Trigger if Active' will not let a new generation come in if previous is active.  If any new event is triggered, the manager will ignore it. Set 'Wait For previous generation' in the properties; the 'Wait for previous generation' allows new application generation come in as APPLWAIT state.  The application will run when the previous active generation has completed.

 

Additional Reference:  WA Agent Troubleshooting and Parameters.

Attachments