SOA 11g: Getting Invalid Addressing Header Error with wsa:Action And SOAPAction Values Difference (Doc ID 1303026.1)

Last updated on AUGUST 13, 2016

Applies to:

Oracle SOA Platform - Version 11.1.1.3.0 and later
Information in this document applies to any platform.

Symptoms


Getting Invalid Addressing header error in BPEL, because wsa:Action header element value generated in outgoing message is different from that of  SOAPAction header value. This error may happen when calling an OSB Proxy service from SOA Composite in 11g, because it is generating SOAPAction value different to wsa:Action.

Below is the exception:


com.sun.xml.ws.addressing.WsaTube validateInboundHeaders
WARNING: A header representing a Message Addressing Property is not valid and the message cannot be processed, Problem header:{http://www.w3.org/2005/08/addressing}Action, Reason:
 {http://www.w3.org/2005/08/addressing}ActionMismatch
 com.sun.xml.ws.addressing.model.InvalidAddressingHeaderException
 at com.sun.xml.ws.addressing.WsaTube.validateSOAPAction(WsaTube.java:413)
 at com.sun.xml.ws.addressing.WsaTube.checkMandatoryHeaders(WsaTube.java:440)
 at com.sun.xml.ws.addressing.W3CWsaServerTube.checkMandatoryHeaders(W3CWsaServerTube.java:37) at com.sun.xml.ws.addressing.WsaTube.checkCardinality(WsaTube.java:386)

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