Java process (JCP/REST/JWP) startup delay in Automic Automation Engine

Products

• CA Automic Workload Automation - Automation Engine

Issue/Introduction

The Automic Automation Engine Java processes like JCP, JCP REST or JWP process experiences significant startup delays, resulting in a wait time of approximately 10 to 11 minutes. In theory, this can happen to any process but it is mostly observed on Java processes.

The process is running (green) in the Service Manager (Dialog) but not in AWI. In other words the process is running but doesn't connect to the other Automation Engine processes.

The issue does not happen when the system is stopped from the Service Manager Dialog, but can happened when the Windows Service or or Linux service (systemd) is stopped.

Environment

• Automic Automation Engine (All supported versions)
• Operating System: Windows and Linux

Cause

The parameter UC_SYSTEM_SETTINGS > RECONNECT_TIME defines the interval, in seconds, at which server processes attempt to establish a connection. A high value, such as 600, significantly can delay the initialization process, if a process was stopped after the PWP. In such case, a STOP message may be left in the PWP queue, as consequence the reconnection timer is triggered and the PWP waits for the timer to expire before querying again for available processes.

Resolution

Solution:

1. Log in to the Automic Web Interface (AWI).
2. Set Client 0 > UC_SYSTEMS_SETTINGS > RECONNECT_TIME = 60
3. Save the changes.
4. Restart the affected Automic Automation Engine processes.

Note: If the intention is to configure a specific agent, RECONNECT_TIME should be apply in the relevant UC_HOSTCHAR_* object rather than using the system-wide variable.

Additional Information

• For further assistance, visit the Contact Broadcom Support page.
• To speak with a customer representative or a Support Engineer, see Contact Support. Scroll to the bottom of the page and click on the respective region.