Notification object with type CALL fails with error code U00019278 or U00045014
search cancel

Notification object with type CALL fails with error code U00019278 or U00045014

book

Article ID: 280978

calendar_today

Updated On:

Products

CA Automic Workload Automation - Automation Engine CA Automic One Automation

Issue/Introduction

There are 2 manifestations of the same error in the code:

1/ The following error is displayed in the Object report, followed by the subsequent occurrence of an exception error in the forced traces of the Work Processes (WPs):

U00020408 U00019278 ??? "L"

----------------------- Stack Trace -----------------------
java.lang.NullPointerException

2/ When the CALL object tries to send a report, but by mistake the report concerns the runID of the CALL itself instead of its parent, the following error is displayed in the JWP log:

20240131/162100.865 - 43     U00045014 Exception 'java.lang.NullPointerException: "null"' at 'com.automic.persistence.impl.ReportPersistenceServiceImpl.getReportBlockSize():141'.
20240131/162100.865 - 43     U00003620 Routine 'com.automic.kernel.impl.StructuredMessageHandler' forces trace because of error.

Environment

Release: 21.x

Component: Automation Engine

Cause

Defect

Resolution

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

Fix version:
Component(s): Automation Engine
Automation.Engine 21.0.10 - Available
Automation.Engine 24.1.0 -  Available

Additional Information

The reference for this fix is: AE-34701
Public description: A bug has been fixed where errors thrown by :SEND_MAIL were not displayed correctly.