Receive AwE-9999 Internal error messages in the RmiServer log

Document ID : KB000089757
Last Modified Date : 14/04/2018
Show Technical Document Details
Issue:
Receive AwE-9999 Internal error messages in the RmiServer log
Resolution:

Detailed Error Message

ErrorMsg: AwE-9999 Internal error (11/4/15 1:00PM)
Details: null
java.lang.NullPointerException
atcom.appworx.shared.data.Job.getStatus(Job.java:697)
atcom.appworx.shared.data.Job.getIntStatus(Job.java:707)
atcom.appworx.server.data.JobsData.ª(JobsData.java:2465)
atcom.appworx.server.data.JobsData.£(JobsData.java:2002)
atcom.appworx.server.data.JobsData.A(JobsData.java:81)
at com.appworx.server.data.JobsData$_E.doRun(JobsData.java:3551)
atcom.uc4.be.threading.AbstractWorker.run(AbstractWorker.java:390)
at java.lang.Thread.run(Thread.java:745)


Symptoms

From the GUI you receive a AwE-9999 error messages and when you look in the RmiServer debug log you will see messages similar to the error above where the Details are null.  However, jobs are still processing.


Cause

The errors are informational errors only that occur because of an inactive job with conditions.  The conditions are not able to evaluate because the job is inactive.  The internal error is thrown when the job refresh cycle sees a job that has a status of STG SKIP, it then tries to check its parent process flow to see if it is running, in which case it will immediately set the jobs status to SKIPPED.  The NullPointerException occurs because the refresh updates come in out of order and the jobs in the process flow come in before the process flow itself, so it gets the exception trying to check the status of the process flow.


Resolution

The errors can be ignored and the issue will resolve itself the next time the job is checked.  This is only a view issue and does not cause any job processing issues.