Posted: 28 Jul 2017 19:34 EDT Last activity: 16 Oct 2018 12:03 EDT
How does Passivation Daemon works ?
Today we setup two new nodes in production, to serve Mashup(IAC) traffic exclusively.The passivation Daemon last run time showed ok unti 3:10 am , but that's the latest last run time. The amount of stale requestors have increased exponentially which forced us to restart nodes to be on safer side at around 4 pm - No out of memory exceptions occured.
While monitoring now at 7 pm, I see the last run time ok - on the busy node. However on the second node - which is less busy and hardly has 10 requestors , it shows passivation daemon's last run time as 4:20 pm.
There are no exceptions in logfiles of any node.
So my questions are:
1) How Passivation Daemon is supposed to work?
Does it wakes up in regular intervals or any other pattern or it wakes up only if it has certain number of pages/requestors to be passivated ?
2) What makes it to fail ?
I reviewed the posts below, but none of them helped.
Passivation allows a requestor, service, or clipboard page to be saved into the PegaRULES database and reactivated later. A background process known as the passivation daemon converts the in-memory state and clipboard information into database rows, making the memory available for other uses. The reverse process is known as activation. Passivation is controlled through prconfig.xml settings. The passivation daemon wakes once a minute to handle passivation.
1. Passivation runs on time interval not on number of records.
2. There could be different reasons for it to fail.
Could you confirm whether none of the stale requestors are cleared? Are you able to see any thread dumps in PegaRULES logs due to this.
Please check whether the Master Agent daemon (also known as “Master for Agents”) running?
You may debug the passivation related issues by enabling DEBUG on below class