My Oracle Support Banner

Troubleshoot known problems related to WS-Addressing in SOA Suite 11g (Doc ID 1171219.1)

Last updated on JANUARY 14, 2019

Applies to:

Oracle SOA Suite - Version 11.1.1.2.0 to 11.1.1.3.0 [Release 11gR1]
Oracle(R) BPEL Process Manager 10g
Information in this document applies to any platform.
***Checked for relevance on 15-July-2013***

Purpose

When integrating with external Web Services  you might face issues related to the WS-Addressing headers in the request and response XML documents used in synchronous request-response scenarios. You have to be aware of those issues, especially when migrating integration solutions from SOA Suite 10g to Fusion Middleware 11g. Most of those scenarios worked successfully with 10.1.3.x.

This document intends to help you identifying the root cause of the problem and provide you with advice how to solve it.

Troubleshooting Steps

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
Purpose
Troubleshooting Steps
 (1) SOA Composite acting as client fails to invoke a Service Provider, that  does not support WS-Addressing headers in the request message for synchronous interactions
 Stack trace
 Explanation
 Solution
 (2) External Service Consumer, that does not support WS-Addressing headers in the response message,  fails to invoke a synchronous operation of a SOA Composite.
 Explanation
 Solution
 (3) Service Provider throws 'wsa:InvalidAddressingHeader' when 'SOAPAction' is defined in the WSDL <binding> element of the service provider interface.
 Stack trace
 Explanation
 Solution
 Summary
 Related Links
References

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.