Skip to main content

This content is closed to future replies and is no longer being maintained or updated.
Links may no longer function. If you have a similar request, please write a new post.

Question

 sri vishnu prabhu (srivishnu)
CAPGEMINI

CAPGEMINI
IN
srivishnu Member since 2016 28 posts
CAPGEMINI
Posted: May 5, 2017
Last activity: May 7, 2017
Posted: 5 May 2017 5:27 EDT
Last activity: 7 May 2017 22:02 EDT
Closed

Unable to restore passivated requestor; error in authorization activation (no legacy context found)

Hi Team,

We installed below mentioned hot fixes in our application.

HFIX-33066- Unauthorized Access Issue
HFIX-23815- Live UI Button missing
HFIX-32457- Authentication Issue

After that we have seen some slowness in the application.

We found log file

2017-05-05 00:27:42,346 [ES PassivationDaemon] [ STANDARD] [ ] [ ] ( mgmt.base.NodeRequestorMgt) ERROR - Passivation Daemon; Requestor: HDDFBEB4DBAB6646BA6CA522B490E0B77 encountered error during passivation; will re-enqueue
com.pega.pegarules.pub.PRRuntimeException: Unable to restore passivated requestor; error in authorization activation (no legacy context found)

Let us why this exception getting displayed.

Thanks in advance

Regards,

Vishnu

***Updated by moderator: Lochan to update Categories***

To see attachments, please log in.
System Administration

Posted: 7 years ago
Posted: 5 May 2017 5:40 EDT
Basavaraj Kadakol (BASAVARAJ)
PEGA
Senior Manager of Technical Support Engineering
Pegasystems Inc.
AU

Hi Vishnu,

Do you have SAML SSO configured the exception could be due to the activation during re-authentication of a timed out session. Please check if there are any configuration issues as SAML SSO.

 

To see attachments, please log in.

We'd prefer it if you saw us at our best.

Pega Collaboration Center has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice