Support Article
Passivation Data and requestors
Summary
In the sreenshot of System Management Application (SMA), one can see several requestors with the expire time in the past. It's normal ?

The time between Created and Expire is 24 hours. Where one can configure this, and have you some preconisation about this.
Error Messages
Not Applicable.
Steps to Reproduce
The steps to reproduce the issue is not known.
Root Cause
Not Applicable.
Resolution
User queries: -In the sreenshot of SMA, user can see several requestors with the expire time in the past. Is it normal ?
Yes, this is normal and it helps you in reporting of the passivated requestors.
-The time between Created and Expire is 24 hours. Where one can configure this, and have you some preconisation about this.
There is an agent 'System Cleaner' which will be run periodically to purge the passivated requestors, so this agent should have been run at your system every 24 hours to purge the entries.
-If searched in SMA on some requestor that are on the directory /.../temp/PassivationData/F/, some are present but without operator ID, or someone are not present.
Passivation of requestor session depends on three factors:
-On timeout
-Never
-NoAuthenticateOnActivate
Go through the below PDN article to know more about Passivation:
https://pdn.pega.com/sites/pdn.pega.com/files/help_v718/procomhelpmain.htm#concepts/concepts2/conceptspassivation.htm
So must be purge the directory /.../temp/PassivationData/ when we restart the jboss instance?
One can purge the passivated files however might lose the previous session
- The System Cleaner agent purge the
/..../temp/PassivationData/ directory ?
System Cleaner will purge the records present in pr_perf_stats table, it does not delete the passivation data from temp directory, there is that privilege to delete it from temp directory.
Published February 20, 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.