StartRunable APM - TargetDate property fails

Document ID : KB000088037
Last Modified Date : 14/04/2018
Show Technical Document Details
Issue:
Affects Release version(s): 3

Error Message :
java.lang.IllegalArgumentException: Too old: Year must be higher than 1800: '0017-07-08 12:16'

When running Automic's Package Manager (APM) command, StartRunable, the TargetDate property fails and an error message similar to the one above is displayed.

Executing the Process Flow will cause the following Java exception to be displayed.

 
109631 2016-01-09 12:16:41.067 apm-sandbox-1 ERROR: com.levatis.apm.uc4.impl.StartRunable com.levatis.apm.uc4.impl.StartRunable.execute(StartRunable.java:40) java.lang.IllegalArgumentException: Too old: Year must be higher than 1800: '0017-07-08 12:16' java.lang.IllegalArgumentException: Too old: Year must be higher than 1800: '0017-07-08 12:16' java.lang.IllegalArgumentException: Too old: Year must be higher than 1800: '0017-07-08 12:16'
at com.uc4.api.DateTime.setDate(DateTime.java:80)
at com.uc4.api.DateTime.<init>(DateTime.java:41)
at com.levatis.uc4.toolbox.uc4api.planning.DateTime.<init>(DateTime.java:9)
at com.levatis.uc4.toolbox.uc4api.planning.Uc4Object.execute(Uc4Object.java:350)
at com.levatis.apm.uc4.impl.StartRunable.execute(StartRunable.java:38)
at com.levatis.apm.uc4.impl.StartRunable.execute(StartRunable.java:13)
at com.levatis.apm.APMCallableCommand.execute(APMCallableCommand.java:27)
at com.levatis.apm.APMTransactionUtil.wrapInTransaction(APMTransactionUtil.java:46)
at com.levatis.apm.APMCallableCommand.call(APMCallableCommand.java:32)
at com.levatis.apm.APMCallableCommand.call(APMCallableCommand.java:9)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:745)

The Java exception indicates that the Java API method 'DateTime' caused the error.
Environment:
OS Version: N/A
Cause:
Cause type:
Configuration
Root Cause: An invalid date format was used, causing the exception.
Resolution:
Use the correct date format of dd-MM-yyyy HH:mm:ss

Fix Status: No Fix

Fix Version(s):
N/A
Additional Information:
Workaround :
N/A