"WSDL not found" when Accessing a WSDL from a BPEL Process Deployed to a Cluster (Doc ID 1059184.1)

Last updated on NOVEMBER 03, 2016

Applies to:

Oracle(R) BPEL Process Manager - Version: 10.1.3.1 and later   [Release: AS10gR3 and later ]
Information in this document applies to any platform.

Symptoms

A BPEL process deployed to a single instance works fine. When the BPEL process is deployed to a cluster, the service is failing on every other call, based on where the request is routed by the load balancer.  The load balancer is set to use "round robin" load balancing. 

In the BPEL Console, from the process' Initiate or wsdl tabs, you see:

In the non-working node:

http://<mycompany.com>:<7777>//orabpel/default/<ProcessName>/1.0/TEST_ProcessName?wsdl:WSDL not found

**Note the two trailing "/" slashes after the port:7777

Upon examination, you see the that the working node uses:

http://<mycompany.com>:<7777>/orabpel/default/<ProcessName>/1.0/TEST_ProcessName?wsdl

**Note the there is only one "/" slash after the port:7777



Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms