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

TK-315040: Large no of brower requestor in SMA



There are large number of requestors observed in the System Management Application (SMA) and errors caused by passivation daemon observed in the log file.
User wants the errors to be addressed.

Error Messages

01:21:16,760 [ES PassivationDaemon] (ternal.async.PassivationDaemon) ERROR - Failed to process passivation queue:


at com.pega.pegarules.exec.internal.util.collections.StringPoolImpl.add(




Steps to Reproduce

Not Applicable.

Root Cause

There was a stackoverflow error due to which Passivation. Daemon stops running building up the stale requestors.


Stackoverflow error is resolved through HFix-20314 and user is suggested to reduce timeout of browser requestors to 10 minutes, which is recommended for environments with multiple processes. This avoids any issues in the future.


Published January 30, 2016 - 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