Question
Cognizant Technology Solutions
IN
Last activity: 26 Sep 2017 7:52 EDT
Thread level data page is refreshed even though the same STANDARD thread of the same service requestor is being used to process multiple requests
Design:
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.
Behavior:
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).
Query:
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***
Cognizant Technology Solutions
IN
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?
Virtusa IT Consulting
AE
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'