Posted: 13 Feb 2017 14:59 EST Last activity: 14 Feb 2017 7:38 EST
Rest/Soap requests - opportunity to detect if client is dying
has Pega 7.1.9 a mechanism, e.g. a callback or another rule, which is called, when the SOAP-Client who has send a request to Pega, is dying or closing the connection? It makes no sense to perform the request to the end, when there is nobody for the answer.
***Updated by moderator: Lochan to update Categories***
There is no known mechanism. We've worked with customers who know their client has an SLA of 2 seconds and want to abort the Service process if Pega exceeds that - since there is no need to send the response as the client has moved on.
Correction: Logging in this morning I see that there is new development being considered to enable "fallback response" on "REST and SOAP synchronous stateless service". This new functionality aims to "make sure that the system will practically always return a sensible result on time, regardless of database slowness, network latencies etc.. The fallback logic is expected to execute very quickly and work without references to databases and other resources that might be (temporarily) unavailable." It would be a "configurable fallback action on a time-period (example: 200 milliseconds)".
This certainly looks like something you could setup to align an SLA with known client SLA's so that Pega responds in time or aborts when processing time exceeds a certain threshold.
Targeting Pega 7.3.
It does look like it will be challenging to kill the child requestor servicing the request and this might not be available in the first pass.