ESS Scheduler Fails Regularly Sending Credentials When Invoking A BPEL Process
(Doc ID 2797782.1)
Last updated on AUGUST 09, 2021
Applies to:SOA on Marketplace - Version 184.108.40.206 and later
Information in this document applies to any platform.
On : 220.127.116.11 version, Core ESS Product Issues
ESS scheduler fails regularly sending credentials when invoking a BPEL process
After migrating BPEL processes and ESS job/schedules from SOACS 18.104.22.168 to SOA MP 22.214.171.124
All ESS jobs invoke BPEL processes via a (private ) Loadbalancer URL and have a username token client policy attached
as the bpel services are secured via username token server policy.
The jobs are of type OneWayWebService
Job scheduling work in general , but often they fail with the error:
XXXXXXXX_server_1.out01145:oracle.as.scheduler.ExecutionErrorException: Oneway Webservice invocation for request 6454 returns unexpected Synchronous SOAPResponse.
XXXXXXXX_server_1.out01145: <Mar 19, 2021 9:05:36,203 AM UTC> <Error> <oracle.as.ess> <ESS-07004>
<Execution error for request 6454. Reason: Oneway Webservice invocation for request 6454 returns unexpected Synchronous SOAPResponse.>
This seem to come from the fact, that the bpel process responds with a 401 (see attched http access log), which usually happens when the basic authentication credential
is missing from the header, eg server asking to provide it.
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