Skip to main content

         This documentation site is for previous versions. Visit our new documentation site for current releases.      

This content has been archived and is no longer being updated.

Links may not function; however, this content may be relevant to outdated versions of the product.

Setting passivation and requestor time-outs

Updated on April 5, 2022

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

When a page is passivated, other pages for that requestor remain in memory, and requestor processing continues normally until that page is needed (such as for read access or for update) and is reactivated into memory. When an entire thread is inactive, the thread context is passivated (including the associated clipboard pages). If the requestor remains idle, eventually the entire requestor context is passivated.

When a requestor is activated, the pages that had previously been passivated remain in storage until they need to be activated. If a page is later re-passivated, it is updated accordingly.

By default, passivation occurs for:

  • Pages that are idle for at least 15 minutes
  • Threads that are idle for at least 30 minutes
  • Requestors that are idle for at least 60 minutes
  • Passivation time-out settings

    Passivation is used to improve system performance by removing pages from the clipboard that have not been accessed by a requestor for a specified period of time.

Have a question? Get answers now.

Visit the Support Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best. is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us