All Jobs on a specific Agent stays in Launched status for 30 to 40 seconds
search cancel

All Jobs on a specific Agent stays in Launched status for 30 to 40 seconds

book

Article ID: 248191

calendar_today

Updated On:

Products

CA Automic Applications Manager (AM)

Issue/Introduction

Jobs that are scheduled on a specific Agent may stay in Launch status for 30 to 40 seconds before going into Running and Finished.

This occurs only on one or more Agents but not all Agents.

Environment

Release : 9.x.x

Component : APPLICATIONS MANAGER

Cause

This is caused by a number of reason that causes a delay in the read and write of a number of Applications Manager directories such as the /out, /tmp, and /run directories.

Resolution

Check if the /out, /tmp, or /run directories contains a large number of files such as in the 100k or more. This could cause a performance issue when reading and writing to these directories.

Additionally, a security patch may be the cause the of delay causing some form of security scan to take place before each time these directories can be read and written to.

"Whitelisting" the $AW_HOME directory for this should resolve the issue.