Autoforecast remains in status preparing
search cancel

Autoforecast remains in status preparing

book

Article ID: 192972

calendar_today

Updated On:

Products

CA Automic Workload Automation - Automation Engine

Issue/Introduction

After an upgrade on the AE to version to version 12.3.2, the Autoforecast does no longer run, it remains indefinitely in version status preparing.

 

WP log can contain the following message:

17 - 20200304/165219.894 - 32     U00045014 Exception 'java.lang.NullPointerException: "null"' at 'com.automic.forecast.model.SimpleForecastable.proposeStartTime():245'.
17 - 20200304/165219.895 - 32     U00003620 Routine 'com.automic.kernel.impl.DefaultExceptionHandler' forces trace because of error.
17 - 20200304/165219.992 - 32     U00045014 Exception 'java.lang.NullPointerException: "null"' at 'com.automic.forecast.model.SimpleForecastable.proposeStartTime():245'.
17 - 20200304/165219.993 - 32     U00003620 Routine 'com.automic.kernel.impl.NATDispatcher' forces trace because of error.
05 - 20200304/165223.255 - U00011043 Activating event  'ADM.SYSTEM_CHECKS_EVERY_1_MIN.EVTT' (RunID:  '0023000479' ).

A forcedTracefile is also created automatically:

UDB:  0.00000
20200304/165219.894 - 32               Unhandled Exception in thread MQWorker-1 ID=32
20200304/165219.895 - 32     U00045014 Exception 'java.lang.NullPointerException: "null"' at 'com.automic.forecast.model.SimpleForecastable.proposeStartTime():245'.
20200304/165219.896 - 32     U00003620 Routine 'com.automic.kernel.impl.DefaultExceptionHandler' forces trace because of error.

Environment

Automation Engine  12.3.2

Cause

This is a bug in the Autoforecast version 12.3.2 could get stuck in Status Preparing when there are tasks with earliest start time.

 

Resolution

This bug is corrected in version 12.3.2 HF2  of One Automation. Upgrade to this version or a higher one to fix this issue.