Passivation allows a requestor, service, or clipboard page to be saved into the PegaRULES database and reactivated later, helping to free up JVM memory, and making more memory available to other requestors.

When a requestor is activated, the pages that had previously been passivated remain on the system and are not affected. If the same page is later re-passivated, it is updated accordingly.

Passivation occurs through three distinct mechanisms:

Page passivation — used for individual pages, threads, or entire requestors

Timeout passivation — used for entire requestors

HTTP session passivation — used to free JVM memory and support failover

Pega Interview Questions