When running a Control-M Application Integrator job, the job may end not ok with the error message "Application Integrator CM: UCM0001 = REST request failed: null". Although previous job runs may have ended Ok. |
When checking on the Control-M Agent's AI_SUBMIT_<job orderid><job run count><date>.log files, there's an entry that reads "IOException error on response Read timed out ". The job is sometimes failing due to the connection endpoint not responding (or it is very slow) sometimes which causes the API call failure. Example of Control-M Agent's AI_SUBMIT_<job orderid><job run count><date>.log file ~AG_LOG\proclog\AI_SUBMIT_0eog7_00001_20200923010000490.log lines from the file: 2020-09-23 06:01:12,937 INFO [Thread-70] (RestUtils.java:541) - httpRest called 2020-09-23 06:01:12,938 INFO [Thread-70] (RestUtils.java:588) - Open receive connection to 'https://<domain>.com/api/v1/workflows/685822' 2020-09-23 06:01:12,938 INFO [Thread-70] (RestUtils.java:165) - Setting content type. 2020-09-23 06:01:12,938 INFO [Thread-70] (RestUtils.java:177) - Setting connection timeout to 90 2020-09-23 06:01:12,938 INFO [Thread-70] (RestUtils.java:693) - Setting header 'API-Token=10340ab6ace4263321775cdf125a996767f0bad2939981dba3ead858c53c902c' 2020-09-23 06:02:43,167 INFO [Thread-70] (RestUtils.java:719) - httpRest: IOException error on response Read timed out 2020-09-23 06:02:43,168 INFO [Thread-70] (RestUtils.java:787) - finally |