Question

5
Replies
4436
Views
HARIKUMAR_ALAMPURU Member since 2011 39 posts
TATA CONSULTANCY SERVICES
Posted: January 4, 2016
Last activity: January 8, 2016
Closed
Solved

Existing Requestor Retrieved - Passivation Issue

Hi All,

I'm troubleshooting a production problem that is happening for a single user. In that process, have enabled the Global DB Trace through SMA and below is the snapshot of first few events that are happening when user loads Pega mashup page.

In the third row, we can see --> Existing Requestor Retrieved message.

  1. Instead of creating a New Requestor, why Pega is trying to retrieve some old requestor ?? From the user standpoint, we have asked the user to clear all the browser cache & cookies and requested for a fresh login but why this is happening ?
  2. How can we clear the old/stale requestors associated with the impacted user ? Ideally the SystemCleaner Agent should have taken care of this ??

Any thoughts ??  By the way we are running on Pega 7.X & HA is configured.


global db trace.png

Thanks

Hari Kumar Alampuru

Message was edited by: Vidyaranjan Av

System Administration
Moderation Team has archived post
Share this page LinkedIn