Process Flow goes to DB ERROR with a Condition Evaluation Error

Products

• CA Automic Applications Manager (AM)

Issue/Introduction

Process Flow goes to DB ERROR with a Condition Evaluation Error

Environment

Release: AAMOS499000-8.0-Automic Applications Manager-OS400 Agent
Component:

Resolution

Detailed Description and Symptoms

A Process Flow will Fail and go to DB ERROR Status after all of its Components have completed successfully.

Investigation

In the RmiServer<timestamp>.log you will see an error like the following:

14:01:53.786 Conditions_AfterOrDelete0: AwE-5072
ErrorMsg: AwE-5072 Condition evaluation error (7/28/11 2:01 PM)
Details: 34054085
Condition evaluation error : 34054085 : java.lang.NullPointerException
    at com.appworx.master.conditions.JobCondition.evaluate(JobCondition.java:260)
    at com.appworx.master.conditions.ConditionManager$AfterOrDeletedConditionsWorker.doRun(ConditionManager.java:143)
    at com.appworx.server.threading.C.run(AbstractWorker.java:349)
    at java.lang.Thread.run(Thread.java:595)
java.lang.NullPointerException

14:01:53.787 Conditions_AfterOrDelete0: .AxRmiServer: observed ErrorMsg: AwE-5072 Condition evaluation error (7/28/11 2:01 PM)
Details: 34054085
34054085

This indicates that there is an After Condition on the Process Flow that is unable to evaluate.

Solution

We don't recommend adding any conditions to Process Flow Headers since a Process Flow is just a container for jobs. To avoid further DB ERROR issues, move the AFTER condition from the Process Flow to a component within the Process Flow.