Skip to main content

This content has been archived and is no longer being updated. Links may not function; however, this content may be relevant to outdated versions of the product.

Support Article

Expecting WS-Addressing header even when WS-Addressing is off



Connect SOAP calls fail with following error message sporadically while calling external services even when WS-Addressing is off.

Error Messages

2014-11-12 16:38:36,665 [ WebContainer : 21] [TABTHREAD6] [ ABC:03.09.09] ( axis2.engine.AxisEngine) ERROR|| ABC12345 - A required header representing a Message Addressing Property is not present
com.pega.apache.axis2.AxisFault: A required header representing a Message Addressing Property is not present
at com.pega.apache.axis2.addressing.AddressingFaultsHelper.triggerAddressingFault(
at com.pega.apache.axis2.addressing.AddressingFaultsHelper.triggerMessageAddressingRequiredFault(
at com.pega.apache.axis2.handlers.addressing.AddressingInHandler.checkForMandatoryHeaders(
at com.pega.apache.axis2.handlers.addressing.AddressingInHandler.extractAddressingInformation(
at com.pega.apache.axis2.handlers.addressing.AddressingInHandler.invoke(
at com.pega.apache.axis2.engine.Phase.invoke(
at com.pega.apache.axis2.engine.AxisEngine.invoke(
at com.pega.apache.axis2.engine.AxisEngine.receive(
at com.pega.apache.axis2.description.OutInAxisOperationClient.handleResponse(
at com.pega.apache.axis2.description.OutInAxisOperationClient.send(
at com.pega.apache.axis2.description.OutInAxisOperationClient.executeImpl(
at com.pega.apache.axis2.client.OperationClient.execute(
at com.pegarules.generated.activity.ra_action_invokeaxis2_25cddb386a1e05c1d332c684e79572c1.step14_circum0(

Steps to Reproduce

Create Connect-SOAP rule with WS-Addressing on and make a call.
Uncheck WS-Addressing and make the call again.

Root Cause

The root cause of this problem is in a third-party product Axis2 integrated with PRPC.

HttpClient is cached in Axis2 version 1.5.1 onwards. The addressing module is engaged with first call of Connector. So, as it reuse the same object to make calls, even though they deselect the option in PRPC UI, the addressing handler is getting cached.


Issue was resolved by HFIX-20023 which adds explicit check using enableWSA value in step-7 of the InvokeAxis2 activity. This disables the addressing for IN messages from activity end. To read the same, Axis2 code has also been modified.

Published January 31, 2016 - Updated October 8, 2020

Was this useful?

0% found this useful

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best.

Pega Community has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice
Contact us