Thread level data page is refreshed even though the same STANDARD thread of the same service requestor is being used to process multiple requests


I have a REST service, from which I'm referring to a data page (via the service activity). The Data Page is a editable thread level one, with NO 'Reload per interaction'/'Limit data page to single page' option selected & also, the data page is not parameterized as well.

I'm also printing the requestor & thread name in the response to confirm which requestor & thread the request is being processed on.

Also, in the service package, I have kept the max no. of active & idle requestors as 3 & idle time to 10 seconds.


When I run the service manually from my pega login, the thread level Data Page is loaded only the 1st time & is not refreshed for successive service executions (confirmed, since the same data from the 1st load is shown in response for next runs as well).

But, when I trigger the service from SOAP UI, the Data Page is refreshed every time (different/new data is returned in response every time). The requestor & thread is the same for all runs (printed & confirmed in response).


Is there any difference in how Pega treats a user requestor & a service requestor? Is the STANDARD thread of a service requestor reinitialized each time while the requestor is reused? What is the explaination/reason for this difference in behavior?

***Edited by Moderator Marissa to update categories***

**Moderation Team has archived post**

This post has been archived for educational purposes. Contents and links will no longer be updated. If you have the same/similar question, please write a new post.


Keep up to date on this post and subscribe to comments

August 28, 2017 - 2:50am


As of my understanding thread is reinitiated for every service request.

September 8, 2017 - 6:54am
Response to SudhakarReddy

Yes, that's I'm guessing as well from the difference in behavior. But is this a confirmed behavior of Pega or an intermittent one, which might differ in higher environments?

August 28, 2017 - 5:25am

Can you please confirm the PRPC version where you are testing the service with datapage?


September 8, 2017 - 6:52am
Response to HabeebBaig

I'm using v7.1.7

September 26, 2017 - 7:52am
Response to AVIRUPBASU

If you are loading the datapage asynchronously in your service activity, there is a hotfix which you can apply and check the behaviour again.

The hotfix reference is 'HFix_27330'