search cancel

JCP and JWP Forces Trace because of FlushUserAction

book

Article ID: 215947

calendar_today

Updated On:

Products

CA Automic Workload Automation - Automation Engine

Issue/Introduction

JCP process and JWP generate some force traces during startup due to the fact that CP and JCP inverse their numbers (JCP becomes CP 001 when it used to be CP 002 and viceversa).
Example of errors in JCP log:

U00003471 The Server 'RUC412#CP001' has successfully been initialized, *** R E A D Y  F O R  R U N ***
U00045014 Exception 'java.lang.NullPointerException: "null"' at 'com.automic.rest.server.RestServerComponent.userRemoved():432'.
U00003620 Routine 'com.automic.kernel.impl.FlushUserAction' forces trace because of error.
U00003450 The TRACE file was opened with the switches '0000000000000000'.
U00003449 Output to the TRACE file is finished.
U00045014 Exception 'java.lang.NullPointerException: "null"' at 'com.automic.rest.server.RestServerComponent.userRemoved():432'.

Example of errors in JWP log:

U00003432 Termination of Server 'TUC412#WP006' initiated.
U00045014 Exception 'java.lang.InterruptedException: "null"' at 'java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.awaitNanos():2109'.
U00003620 Routine 'com.automic.kernel.impl.NetworkMessageDispatcher' forces trace because of error.
U00003450 The TRACE file was opened with the switches '0000000000000000'.

Environment

Release : 12.3

Component : AUTOMATION ENGINE

Cause

Bug

Resolution

Workaround:

Ignore JCP and JWP force traces

Solution:

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

Fix version:
Component(s): Automation.Engine 

Automation.Engine 12.3.7 - Available