Cannot Invoke NON-DEFAULT Version of Composite after SOA Restart

(Doc ID 1460803.1)

Last updated on MARCH 08, 2017

Applies to:

Oracle(R) BPEL Process Manager - Version and later
Information in this document applies to any platform.


A composite is deployed with two different revisions, 1.0 and 2 .0. Revision 2.0 is set as default. Using SoapUI both revisions of the composite can be invoked, however,
after restarting SOA server only the default revision 2.0 can be invoked. Invoking revision 1.0 returns a HTTP 400 error and the following error appears in the log files:

Looking at the end point of the non default version, one can see that the URL changes after SOA restart, making the invocation fail. For example,

After deployment and before SOA restart:!1.0*soa_42aa1742-abe2-4ba9-bb69-a54133c15cf1/basavachemtest_client_ep

After SOA restart:!1.0/basavachemtest_client_ep

The first URL shows label *soa_42aa1742-abe2-4ba9-bb69-a54133c15cf1 next to version !1.0


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