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

Addressing error in Connect-Soap



In a Connect-Soap with WS-Addressing unchecked suddenly shows a fail in step 17 of the InvokeAxis2 activity:

A required header representing a Message Addressing Property is not present.

Error Messages

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.invokeHandler(
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_58dbca272054d891f3559ad0fb53c832.step14_circum0(
at com.pegarules.generated.activity.ra_action_invokeaxis2_58dbca272054d891f3559ad0fb53c832.perform(
... 84 more

Steps to Reproduce

Call a Soap-connect rule (invokeAxis2).

Root Cause

A defect in Pegasystems’ code or rules as changed to adopt praxis2-1.6.2.jar introduced in Pega 7.1.8 were missing in Pega 7.2.2.


Apply HFix-33437.

Additional Installation Instructions

Note: Old jar has to be deleted before importing the hotfix.

1. Take a database back up.
2. Execute the following delete queries :

delete from pr_engineclasses where pzclass= 'praxis2-1.6.2.jar'
delete from pr_engineclasses where pzjar= 'praxis2-1.6.2.jar'

3. Import the fix.
4. Clean the temp folder and Restart server.

Published May 10, 2017 - 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