Skip to main content
Contact a Moderator

Discussion

1
Replies
2758
Views
 Cristy Lupato (CristyL7180)
Comptech Associates, Inc

Comptech Associates, Inc
US
CristyL7180 Member since 2015 2 posts
Comptech Associates, Inc
Posted: February 2, 2016
Last activity: March 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.

 

Reporting
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 Discussion, please write a new Discussion.
Posted: 5 years ago
Posted: 16 Mar 2016 12:03 EDT
Stavros Dimitriou (dimis)
PEGA
Global Tech Enablement, Senior Instructor
Pegasystems Inc.
DE

Ηι CristyL7180


not sure about this. 

I will forward your question to the relevant SME. They will get back to you.


Regards

DIMIS

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