Support Article
Service-REST needs timeout and requestor terminated.
SA-28535
Summary
The requirement in this case is the Service REST that is handling calls from consumers needs to have a 6-second timeout.
If the Service Activity can not complete in six seconds, it needs to terminate.
The SLAs for the consumers is under two seconds. So, the consumer who initiated the request has already terminated it and is "no longer listening". But, the request is still churning in Pega.
User wants to get these requestors back into the pool.
User requires to know how can this be implemented in Pega? Needs to be synchronous.
The service activity has internal connect calls to other applications, so there might be something that can be done on those steps in the activity. But, is there any configuration that can handle terminating an active.
Error Messages
Not applicable
Steps to Reproduce
1. Configure prconfig.xml with the entries :<env name="timeout/application" value="6" />
<env name="Initialization/PersistRequestor" value="Never" />
3. Trigger the service from SOAP UI or any other tool. The application should timeout in 6 seconds, but it does not.
Root Cause
This issue was determined to be a product enhancement request.
Resolution
An enhancement request, FDBK-16764, has been created for consideration by Pega Product Management.
Published October 5, 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.