We are using PRPC 6.1 SP2. We use external authentication for logon. We need to make changes in few DB tables if session times out. We made the changes in TimeOut activity in Authentication service rule form. But if timed out requestor closes the browser window then it would be a problem. How does pega determine if the requestor session timed out? Would there be any agent which tracks all requestors events?
A background process known as the passivation daemon wakes once a minute to handle passivations.
A daemon is a reserved background Java thread that executes as a BATCH requestor type, like agents, but is not defined by an agents rule (Rule-Agent-Queue rule type) and is not a full requestor. These threads operate continuously, automatically, and generally invisibly. Pega includes 6 such daemons and passivation daemons is one of them.
I'm not sure the prpc server even knows the difference between a requestor where user actually has the screen showing on their browser, and a requestor where the user closed the browser. Am I right ?
If so, then to detect the difference, you may need to have a keep-alive scenario orchestrated with ajax from the browser, the server side of which responds by updating a property on a declare-page, so that your server-side "daemon" can look for stale values of that property as evidence that the browser is no longer there. /Eric