Support Article

Addressing error in Connect-Soap

SA-36865

Summary



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(AddressingFaultsHelper.java:463)
at com.pega.apache.axis2.addressing.AddressingFaultsHelper.triggerMessageAddressingRequiredFault(AddressingFaultsHelper.java:389)
at com.pega.apache.axis2.handlers.addressing.AddressingInHandler.checkForMandatoryHeaders(AddressingInHandler.java:315)
at com.pega.apache.axis2.handlers.addressing.AddressingInHandler.extractAddressingInformation(AddressingInHandler.java:299)
at com.pega.apache.axis2.handlers.addressing.AddressingInHandler.invoke(AddressingInHandler.java:178)
at com.pega.apache.axis2.engine.Phase.invokeHandler(Phase.java:340)
at com.pega.apache.axis2.engine.Phase.invoke(Phase.java:313)
at com.pega.apache.axis2.engine.AxisEngine.invoke(AxisEngine.java:264)
at com.pega.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:170)
at com.pega.apache.axis2.description.OutInAxisOperationClient.handleResponse(OutInAxisOperation.java:364)
at com.pega.apache.axis2.description.OutInAxisOperationClient.send(OutInAxisOperation.java:421)
at com.pega.apache.axis2.description.OutInAxisOperationClient.executeImpl(OutInAxisOperation.java:229)
at com.pega.apache.axis2.client.OperationClient.execute(OperationClient.java:165)
at com.pegarules.generated.activity.ra_action_invokeaxis2_58dbca272054d891f3559ad0fb53c832.step14_circum0(ra_action_invokeaxis2_58dbca272054d891f3559ad0fb53c832.java:3688)
at com.pegarules.generated.activity.ra_action_invokeaxis2_58dbca272054d891f3559ad0fb53c832.perform(ra_action_invokeaxis2_58dbca272054d891f3559ad0fb53c832.java:292)
... 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.

Resolution



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 April 21, 2017 - Updated May 10, 2017

Have a question? Get answers now.

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