Close popover
Jon Garfunkel (JonnyGar)
BNY Mellon
Vice President, BPM CoE
BNY Mellon
JonnyGar Member since 2009 91 posts
BNY Mellon
Posted: March 10, 2015
Last activity: July 17, 2017

When are passivated requestors restored?

to my recollection, a passivated requestor is restored when a user re-accesses Pega but his session requestor is not in memory, so it's pulled from the database.

One of our 7.1.5 QA systems here has 108 passivated requestors, and 14 active requestors.

I set DEBUG on com.pega.pegarules.session.internal.mgmt.base.NodeRequestorMgt on it.

I see messages at a rate of >3/second telling me "Retrieved requestor: A5D438FE740B5551AAA3584DBBCCEBC64"

Why would it be doing that?

Also, when I look at these A* requestors, they have a number of pages on the Clipboard, like pyResponseAttachmentPage and pySearchPage.

This is created by InvokeHTTPConnector and other connectors. pySearch i used by pySearchHTTPConnect.

This connector has Maintain Session unchecked. So I'd expect this requestor to be deleted after use.

So why is it passivated? And why is it regularly being retrieved, when I turn on that logging?

I can view the Passivated Requestors on the SMA. Is there no way to delete them? I'm wondering if the passivated requestors is related to our problem triggering the pzUnknownSessionAlert stream (see SR-128597 & SR-128894)

***Updated by moderator: Marissa to close post***
System Administration
Moderation Team has archived post,