Since updating their REST Webservice Agent to v4.6.4 on their environment, REST jobs that were working fine before are no longer working correctly.
Agent log:
20221102/102515.663 - U02000005 Job 'G65.LCI.RECON.JOBS.REST.FDS.STATUS.TESTING-MIKE' with RunID '1104152069' started. 20221102/102515.663 - U02000003 Job 'G65.LCI.RECON.JOBS.REST.FDS.STATUS.TESTING-MIKE' started with RunID '1104152069'. 20221102/102515.814 - U00029000 Report '1104144287' for file '/var/uc4/agent-ra-rest/out/PLOG_ODOYFPBH.TXT' has been started. 20221102/102515.859 - U00029001 Report '1104148219' ended normally. 20221102/102516.118 - U02000009 Job 'G65.LCI.RECON.JOBS.REST.FDS.STATUS.TESTING-MIKE' with RunID '1104152069' ended with return code '2'. 20221102/102516.157 - U00029001 Report '1104144287' ended normally. 20221102/102516.220 - U02001026 Job 'G65.LCI.RECON.JOBS.REST.FDS.STATUS.TESTING-MIKE' with RunID '1104152069' has been removed from the job table.
This error may come in the PLOG of the Job:
java.lang.Exception: Response query parse error: There was an error executing the query to retrieve variables from the response.
First part of the response being processed:PD94bWwgdmVyc2lvbj0i
Error from the execution of the query:
ERROR Cannot execute query.
ch.ethz.mxquery.exceptions.DynamicException: Error creating validating input: org.xml.sax.SAXParseException; lineNumber: 1; columnNumber: 1; Content is not allowed in prolog.
Used script:
/Executions/Execution/CurrentStatus/normalize-space(text())
at java.base/jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at java.base/jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance(Unknown Source)
at java.base/jdk.internal.reflect.DelegatingConstructorAccessorImpl.newInstance(Unknown Source)
at java.base/java.lang.reflect.Constructor.newInstance(Unknown Source)
......
at com.uc4.ex.ThreadPool$RunnableDecorator.run(ThreadPool.java:53)
at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source)
at java.base/java.util.concurrent.FutureTask.run(Unknown Source)
at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
at java.base/java.lang.Thread.run(Unknown Source)
In the Job Report we may find similar to :
2022-11-02 10:25:16 pool-1-thread-6637: REST: There was an error executing the query to retrieve variables. Part:response_part_0\_ 2022-11-02 10:25:16 pool-1-thread-6637: REST: executeQuery (exit 2) 2022-11-02 10:25:16 pool-1-thread-6637: REST: An error occurred - processing the response query Response query parse error: There was an error executing the query to retrieve variables from the response. First part of the response being processed:PD94bWwgdmVyc2lvbj0i Error from the execution of the query: ERROR Cannot execute query. ch.ethz.mxquery.exceptions.DynamicException: Error creating validating input: org.xml.sax.SAXParseException; lineNumber: 1; columnNumber: 1; Content is not allowed in prolog. Used script: /Executions/Execution/CurrentStatus/normalize-space(text()) 2022-11-02 10:25:16 An error occurred - processing the response query 2022-11-02 10:25:16 Response query parse error: There was an error executing the query to retrieve variables from the response. 2022-11-02 10:25:16 First part of the response being processed:PD94bWwgdmVyc2lvbj0i 2022-11-02 10:25:16 Error from the execution of the query: 2022-11-02 10:25:16 ERROR Cannot execute query.
RA core : 12.3.9
RA REST Webservice Solution 4.6.4
This is a defect introduced in Solution 4.6.4
This bug is corrected in Solution 4.6.5 of the RA REST Webservice Agent.