Scheduler going To Long Running Status
(Doc ID 2491433.1)
Last updated on MARCH 28, 2019
Applies to:SOA Suite Cloud Service - Version N/A and later
Information in this document applies to any platform.
The scheduler job is going to long running status and SOA composite is not picking the files from SFTP location.
When a async recurring job is created for ex: with name "XXX_JOB" which invokes SOA composite with name "XX" let's say for every 30 minutes.
"XYZ" (parent composite) goes to faulted state because child composite invocation fails with 502 gateway timeout error.
Fault in parent composite causes ESS job to get stuck in running state,But it also leads to new jobs not triggering at designated time.
Only way to fix this is to cancel and resubmit the request. But this lead of outage and loss of business.
Is this an expected behaviour?
Could notice the below in the logs
oracle.fabric.common.FabricInvocationException: oracle.j2ee.ws.client.jaxws.JRFSOAPFaultException: Client received SOAP Fault from server : Invalid SOAPResponse message: wsa:relatesTo=null, wsa:Action=null
In the diagnostic logs :
ESS-07367 Error validating Job-Callback Policy Subject registration with OWSM Policy Access Point for request 489037.
ESS-07328 Error processing WebServiceJob callback message in ProviderRequest.
Error while invoking endpoint "http://xx.xx.xx.xx:xx/ess-wsjob/async/callback" from client
Unable to dispatch request to http://xx.xx.xx.xx:xx/ess-wsjob/async/callback due to exception
<suppl_detail>oracle.j2ee.ws.client.jaxws.JRFSOAPFaultException: Client received SOAP Fault from server : Invalid SOAPResponse message: wsa:relatesTo=null, wsa:Action=null
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document