Rest webservice job fails to execute

book

Article ID: 222383

calendar_today

Updated On:

Products

CA Continuous Delivery Automation - Automation Engine

Issue/Introduction

If the user tries to run a RA Rest jobs agains the following CDA/AE Endpoint like for instance 'https://parawb.sap.local:13444/cda/api/data/v1/executions' with the credentials entered. The jobs never ends, it stays activating and the report activity remains in status transferring. The jobs cannot be cancelled manually.
To stop it, the status must be changed manually or the RA Rest Agent must be stopped and restarted (the jobs goes then into the status aborted).
The Report of this Job is empty. The Report is not created in the agent temp folder.

Two scenarios are possible either a restart of the agent is restarted and the jobs ends:

This behavior but with different results in the PLOG when the jobs ends with ENDED_LOST - ended undefined. 

+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

2021-04-09 16:59:19 - U00011172 JOB_INF was sent to Agent 'MUNTEST000594_WSSREST01'. Job name 'JOBS.WEBSERVICEREST.REST.DEV_ARA' (RunID '0001660003') job status 'Active'
2021-04-09 16:59:23 - U00011175 Negative JOB_INF was sent from Agent 'MUNTEST000594_WSSREST01'. Job name 'JOBS.WEBSERVICEREST.REST.DEV_ARA' (RunID '0001660003'), old job status 'Active', new job status 'ENDED_LOST - ended undef

+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

or when the job ends with ENDED_NOT_OK Runid 1661009 (remains running 20 minutes!!)

+++++++++++++++++++++++++++++++++++++ Start of Runtime Exception ++++++++++++++++++++++++++++++++++++
com.uc4.extensibility.iface.CITServerException: Connection must not be empty
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
at java.lang.reflect.Constructor.newInstance(Constructor.java:423)
at org.codehaus.groovy.reflection.CachedConstructor.invoke(CachedConstructor.java:83)
at org.codehaus.groovy.runtime.callsite.ConstructorSite$ConstructorSiteNoUnwrapNoCoerce.callConstructor(ConstructorSite.java:105)
at org.codehaus.groovy.runtime.callsite.AbstractCallSite.callConstructor(AbstractCallSite.java:250)
at REST.runJob(WebServiceRest.groovy:2952)
at com.uc4.extensibility.types.CITAgent.dispatchJob(CITAgent.java:258)
at com.uc4.ex.cit.CITJob.execute(CITJob.java:195)
at com.uc4.ex.Job.run(Job.java:461)
at com.uc4.ex.ThreadPool$RunnableDecorator.run(ThreadPool.java:53)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at java.lang.Thread.run(Thread.java:748)
++++++++++++++++++++++++++++++++++++++ End of Runtime Exception +++++++++++++++++++++++++++++++++++++

Cause

This a bug of the One Automation Engine (correction description with cause).

A problem has been fixed where an invalid encrypted value in a connection object caused the RA agent to hang.  The Job stayed active for 1200 seconds, then it failed with a timeout error. Now the Job fails immediately in this case and processing is not blocked anymore.

Environment

One Automation AE 12.3.3 
RA Rest solution 4.5.2+build.547 and RA Core 12.3.3

Resolution

This bug is corrected in Versions

AE 21.0.0 available end of September 2021

AE 12.3.7 available end of october 2021

Update to one of these two versions or higher, once they will be issued.