Skip to main content

This content is closed to future replies and is no longer being maintained or updated.
Links may no longer function. If you have a similar request, please write a new post.

Discussion

 Cristy Lupato (CristyL7180)
Comptech Associates, Inc

Comptech Associates, Inc
US
CristyL7180 Member since 2015 2 posts
Comptech Associates, Inc
Posted: Feb 2, 2016
Last activity: Mar 16, 2016
Posted: 2 Feb 2016 12:59 EST
Last activity: 16 Mar 2016 12:03 EDT
Closed

requestor timeout

We have entered the following DSS in Pega 7.1.7

prconfig/initialization/httplockretryinterval = 100000 because of long running reports.  Is this still applicable in this platform? Or do we use the prconfig/timeout/application/default?

We still get the error Unable to synchronize requestor within 120 seconds using the former.

 

Thanks.

 

To see attachments, please log in.
Reporting

Related content:

Related content has not currently been identified for this post.

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

Pega Collaboration Center 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