Question

2
Replies
149
Views
Karthik Kummera (Karthik K)
PEGA
Senior Demo Engineer, Support
Pegasystems Inc.
IN
Karthik K Member since 2016 36 posts
PEGA
Posted: January 16, 2018
Last activity: January 17, 2018
Posted: 16 Jan 2018 5:47 EST
Last activity: 17 Jan 2018 6:20 EST
Closed

How Application would be knowing -- Service responded with an exception but sent fault content in Body Tags.

https://pdn.pega.com/support-articles/connect-soap-does-not-capture-error-messages

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***

Data Integration
Moderation Team has archived post, This thread is closed to future replies. Content and links will no longer be updated. If you have the same/similar Question, please write a new Question.