Jobs on RA Agents that have connection objects on the Job panel fail sporadically
search cancel

Jobs on RA Agents that have connection objects on the Job panel fail sporadically

book

Article ID: 84971

calendar_today

Updated On:

Products

CA Automic Workload Automation - Automation Engine

Issue/Introduction

Error Message :
Avaloq-Agent-AvaloqAgent-2-3-1-hf-3-null-password-given-logon-denied

This bug happens only when using RA Agents that have a connection Object in the Job definition (e.g. the Avaloq Agent) and some values from the Connection Object are missing.

You will get a null password given error sporadically, it does not happen very frequently.

What happens in Detail is this:

 
ExecuteJob.runJob(com.uc4.extensibility.types.CITAgent agentRef,
com.uc4.extensibility.iface.ICITServerFunctions serverCom,
com.uc4.extensibility.container.LaunchData launchData,
java.util.Map prompts,
com.uc4.extensibility.objs.ConnectionsData conData )):
calls the following line:
jdbcCon = getConnection(conData.getConnectionData ('AVConnectionValue'))
and
conData.getConnectionData ('AVConnectionValue') returns:
loginIDValue: null => Even if it is set

Environment

OS Version: N/A

Cause

Cause type:
Defect
Root Cause: This can occur when there is an incomplete connection object (some values are missing). The problem happens very infrequently and is a very sporadic error.

Resolution

Update to a fix version listed below or a newer version if available.

Fix Status: Released

Fix Version(s):
Component(s): RA Core

Automation Engine 12.1.0 - Available
Automation Engine 12.0.3 - Available
Automation Engine 11.2.6 - Available
Automation Engine 10.0.8 HF8 - Available

Additional Information

Workaround :
Restart the failed task.