Skip to main content
This content has been archived and is no longer being updated. Links may not function; however, this content may be relevant to outdated versions of the product.

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" />

2. Create a REST service in the same node and put a wait in the service activity for 10 seconds.
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. 

 

 

Suggest Edit

Published October 5, 2016 - Updated October 8, 2020

Did you find this content helpful? Yes No

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.

We'd prefer it if you saw us at our best.

Pega Community has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice
Contact us