SMA displays Requestors older than 3 days
We configured a new node recently for serving mashup/IAC traffic exclusively . On that node, the requestor cleanup doesn't happen accurately. There are many requestors with Last Input: existing requestor retrieved. systemcleaner is running everyday on that node with no exceptions. Unless we restart the node the requestor count doesn't reflect the real active users. Any ideas? Thanks.
Pegasystems Inc.
IN
Hi,
Please refer to below link looks like similar issue.
https://community.pega.com/support/support-articles/passivated-data-was-not-deleted-system-cleaner
Thank You
Pegasystems Inc.
US
Hi,
It's very strange to have requestors sitting out there for so long with a last action of "Existing requestor retrieved". You have several from 7/19 and 7/20 and it looks like the screen shot was probably taken on 7/21.
What version of PRPC?
Have you modified any of the passivation settings? SMA -> Node -> Administration -> Configuration Management:
initialization/persistrequestor = OnTimeout
I also noticed in the SMA screen shots the last action of one of the requestors was a call to "Activity=Logoff". This one is also from 7/19 and it should never be the last activity called.
Are you coding a PRPC logoff on a window event like onUnload or onBeforeUnload in the page that contains the Mashup div? Are you using code like this:
pega.web.api.doAction("[GadgetName]", "logoff");
When not using PRGateway this ends up calling Code-Security.Logoff and will result in a call to Code-Security.EndSession via a redirect. The target for the calls is the Iframe and these can end up being aborted by the browser because the window is closing/closed when trying to trigger the logoff from a window unload event. This browser abort can leave the requestors in a strange state. I do have to admit I have not seem them stay for days like this though.
Let me know how you are coding this logoff for the Mashups.
ConEdison
US
Hi Chris,
The screenshot was taken yesterday, 7/24 just before submitting the post. Yeah requestors from 7/19, that's what alarmed me, something is wrong.
PRPC version: 7.1.8. The code base has cpm 7.1.3 too. But the iac stack just built on pegaRULES app, no cpm.
The setting initialization/persistrequestor = OnTimeout is not changed, it's a DSS and the same value for all of our nodes - attached a screenshot too.
The prpc logoff is coded on a button click. When the user logs out of the top level application - the logoff to PRPC is fired.
var logoffURL = PegaGatewayURL + "?pyActivity=Code-Security.LogoffMashup";
xmlhttp = new XMLHttpRequest();
xmlhttp.open("GET", logoffURL, false);
xmlhttp.send();
and also the userworkform is modified to set : pega.util.Event.removeListener(window, "beforeunload",pega.u.d.harnessOnBeforeUnload);
You and myself coded this part 4 months ago to prevent issues with firing pydeletedocumentpg after logoff.