If a webservice response contains a SOAP header with mustUnderstand="1", JAX-RPC invocation fails with error "MustUnderstand header not processed". (Doc ID 1182143.1)

Last updated on JUNE 09, 2016

Applies to:

Oracle WebLogic Server - Version 10.3 to 10.3.3
Information in this document applies to any platform.
***Checked for relevance on 29-07-2014***
If a Webservice response contains a SOAP header with mustUnderstand="1", and the client fails with the error of "MustUnderstand header not processed", you may have this issue. Web service security is turned off, and the web service uses a custom SOAP header. If the web service client called an Artix web service, the custom SOAP header may carry "mustUnderstand="1".


Symptoms

You will notice the below error in the logs:

[java] Caught Unexpected Exception
[java] java.rmi.RemoteException: SOAPFaultException - FaultCode [{http://xyz.abc.com/customheader}MustUnderstand] FaultString [MustUnderstand header not processed '{http://xyz.abc.com/customheader}WSResponseHeader']
FaultActor [null]No Detail; nested exception is:
[java] javax.xml.rpc.soap.SOAPFaultException: MustUnderstand header not processed '{http://xyz.abc.com/customheader}WSResponseHeader'
[java] at com.abc.xyz.soapheader.myapp.MyappSoapHeaderPortType_Stub.fooCallbackPoll(Unknown Source)
[java] at com.abc.xyz.soapheader.myapp.client.Client.main(Unknown Source)
[java] Caused by: javax.xml.rpc.soap.SOAPFaultException: MustUnderstand header not processed '{http://xyz.abc.com/customheader}WSResponseHeader'
[java] at weblogic.wsee.util.HeaderUtil.checkMustUnderstandHeader(HeaderUtil.java:57)

Changes

N/A

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