Soap service is getting terminated with the below exception.
com.pega.pegarules.pub.services.RemoteApplicationException: SOAP service failed, error:The MessageContext does not have an associated SOAPFault.
Soap service is sending the message in the body. If we comment the step(that handles the soap fault content in invokeaxis2), we are receiving the fault content in Body Tag and no exception.
But, my question is in the response body -- tags are like respblock , respdesc but no where related to fault tag. How application would be knowing, service responded with an exception and sent fault details in the body tag.
Are there any http status codes or any other, that indicates service exception.
Could you please explain.
***Updated by moderator: Lochan to add Categories***
Yes... Sudhakar. But, in service response(if we comment the step in invokeaxis2 activity that handles the soap fault) -- there are no tags related to fault(what you mentioned in your answer.)
It is ending with an exception(if we dont comment the step in invokeaxis2 and leave as it is). My question is, as there are no tags related to fault in the body tag, How Application would be knowing, as fault content is received in the Soap Body response and its failing while executing the step that handles the fault content.