Lifespan of Read Only Data Pages?
Hello,
A developer on my program was mentioning that Read Only Data Pages stay in memory for the lifespan of the requestor, even if we manually Page-Remove them. Is this true?
For things like Batch Requestors and Requestor Pools, don't they keep the same Requestor open (and same thread) how would we handle situations where we're seeing memory growing?
In my instance: I'm getting many PEGA0016 Alerts on a Queue Processor's requestor that's executing the same activity over and over on the same thread in the same requestor.
Any guidance would be appreciated.
Pegasystems Inc.
US
You can specify the scope of the Data Page to be either Thread, Requestor, or Node. You can also specify a refresh strategy on the Load Management tab of the rule form if you want it to expire after a certain period of time and reload. When it expires though, I think it would stay on the Clipboard but then reload if it is accessed after the expiration.
Accenture Federal Services
US
Understood on the Scope front. I'm specifically interested in the question from a memory perspective (whether that be directly on the clipboard or the underlying memory.) I've Page-Removed Read Only Data Pages in both Thread and Requestor contexts that I have suspicions remain in memory.