Skip to main content

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.

Support Article

Unable to passivate page pxRequestor



During failover testing in a high availability environment the user is forced to log back into the system.

When reviewing the logs the following error has been identified that could be the cause of the forced re-login.

Unable to passivate page 'pxRequestor' on thread 'null' in requestor 'H364BF796484E78BBB9FD81AB9AE515FF'.

It appears as though the pxRequestor page cannot be serialized and may be the cause of the force relogin during the failover test.

Error Messages

The following error appears in the logs.

com.pega.pegarules.session.external.mgmt.PageCannotBeSerializedForPassivationException: Unable to passivate page 'pxRequestor' on thread 'null' in requestor 'H364BF796484E78BBB9FD81AB9AE515FF'. The following items were not serializable: [Property not serializable: "pxRequestor.STSConfigContext" Class: "com.pega.apache.axis2.context.ConfigurationContext"].

Steps to Reproduce

  1. Setup High Availability (HA) environment.
  2. Setup security to use Axis2. Exam logs periodically for passivation exception.

Root Cause

A defect in Pegasystems’ code or rules.

Instead of caching the service context and STS config context in requestor page, cache these object in a data page.


Apply HFix-34752.

Published June 19, 2017 - Updated October 8, 2020

Was this useful?

0% found this useful

Have a question? Get answers now.

Visit the Collaboration 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.

Pega Community has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice
Contact us