Support Article
TK-315040: Large no of brower requestor in SMA
SA-17178
Summary
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:
java.lang.StackOverflowError
at com.pega.pegarules.exec.internal.util.collections.StringPoolImpl.add(StringPoolImpl.java:277)
at com.pega.pegarules.data.internal.clipboard.StandardEnvironmentAdapter.addStringToPool(StandardEnvironmentAdapter.java:67)
at com.pega.pegarules.data.internal.clipboard.directstream.DirectStream.getPropertyOffset_DSCOnly(DirectStream.java:2300)
at com.pega.pegarules.data.internal.clipboard.directstream.DirectStream.getPropertyOffset_DSCOnly(DirectStream.java:2302)
Steps to Reproduce
Not Applicable.
Root Cause
There was a stackoverflow error due to which Passivation. Daemon stops running building up the stale requestors.
Resolution
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
Have a question? Get answers now.
Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.