Java-based agent does not start with wrong configuration in JCP_ENDPOINT.

Products

• CA Automic Workload Automation - Automation Engine

Issue/Introduction

A Java-based agent does not start if the JCP_ENDPOINT is wrongly configured. In this specific case, the entry was just the server name and not a URL like https://SERVER_NAME:PORT

The agent log shows the following Java exception:

U02000401 Received JCP server list: 'SERVER_NAME'
U00045014 Exception 'java.lang.ArrayIndexOutOfBoundsException: "Index 1 out of bounds for length 1"' at 'com.uc4.jcp.ha.JcpConnectionInfo.createFromUrl():55'.
U00003620 Routine 'com.uc4.ex.MessageDispatcher' forces trace because of error.
U00003450 The TRACE file was opened with the switches '0000000000000000'.
U00003449 Output to the TRACE file is finished.

 

Environment

Automic Workload Automation 21.0.X, 24.X.X

Cause

Configuration issue.

Resolution

The JCP_ENDPOINT needs to be a URL, i.e. https://SERVER_NAME:PORT

The entry in the agent log will then show as:

U02000401 Received JCP server list: 'https://SERVER_NAME:PORT'