Support Article
Expecting WS-Addressing header even when WS-Addressing is off
SA-5375
Summary
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 acc-pega62.hosting.corp|xxx.219.xxx.6|Rule-Connect-SOAP.xxx-Int-xxx-BankAcct-xxxService-.GetBban 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(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.invoke(Phase.java:318)
at com.pega.apache.axis2.engine.AxisEngine.invoke(AxisEngine.java:256)
at com.pega.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:162)
at com.pega.apache.axis2.description.OutInAxisOperationClient.handleResponse(OutInAxisOperation.java:364)
at com.pega.apache.axis2.description.OutInAxisOperationClient.send(OutInAxisOperation.java:417)
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_25cddb386a1e05c1d332c684e79572c1.step14_circum0(ra_action_invokeaxis2_25cddb386a1e05c1d332c684e79572c1.java:3404)
..more..
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.
Resolution
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
Have a question? Get answers now.
Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.