Support Article
Connect SOAP does not capture error messages
SA-14503
Summary
Connect SOAP to the third party Service end does not capture the error messages.
Error Messages
Caused by: java.lang.IllegalArgumentException: The MessageContext does not have an associated SOAPFault.
at com.pega.apache.axis2.util.Utils.getInboundFaultFromMessageContext(Utils.java:455)
at com.pega.apache.axis2.description.OutInAxisOperationClient.handleResponse(OutInAxisOperation.java:371)
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_4b10dba45aa4cd1bc2f9eca0744d3db2.step14_circum0(ra_action_invokeaxis2_4b10dba45aa4cd1bc2f9eca0744d3db2.java:3928)
at com.pegarules.generated.activity.ra_action_invokeaxis2_4b10dba45aa4cd1bc2f9eca0744d3db2.perform(ra_action_invokeaxis2_4b10dba45aa4cd1bc2f9eca0744d3db2.java:291)
.
.
.
Steps to Reproduce
1. Create a Connect-SOAP to a third party service.
2. Ensure that it returns Fail messages.
Root Cause
The root cause of the problem is with the third party service that is called using Connect-SOAP which does not send the error messages in <SOAP-ENV:Fault> tags, instead the SOAP mesage body is sent which causes the issue.
Resolution
Modify the service end to send the fault response as a part of <SOAP-ENV:Fault> tags instead of sending in the message body.
Published October 5, 2015 - Updated December 2, 2021
Have a question? Get answers now.
Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.