Question

3
Replies
295
Views
JRWells_Virtusa Member since 2005 8 posts
Virtusa Corportaion
Posted: 4 years ago
Last activity: 4 years ago
Closed
Solved

Passivation exceptions increase after upgrade to 7.2.1

My PegaCLOUD instance has had an increase of the passivation exception below since upgrading to 7.2.1.  According the the stats collected by the Diagnostic Cloud, occurences have increased from 1600+ last week to 7400+ this week.  The environment is non-Production (dev environment with 5 users max throughout the day).  

What does this exception mean, and what can be done about it?

Sample log file attached from 8/24.

STACK TRACES
  (root cause)
Type com.pega.pegarules.pub.PRRuntimeException
   
Message Unable to restore passivated requestor; error in authorization activation (no legacy context found)
   
Stack 
at com.pega.pegarules.session.internal.authorization.SessionAuthorization.activate(SessionAuthorization.java:388)
at com.pega.pegarules.session.internal.authorization.Authorization.activate(Authorization.java:517)
at com.pega.pegarules.session.internal.mgmt.base.ThreadPassivation.activateThread(ThreadPassivation.java:845)
at com.pega.pegarules.session.internal.mgmt.base.ThreadPassivation.configureThreadImpl(ThreadPassivation.java:298)
at com.pega.pegarules.session.internal.mgmt.PRThreadBase.configureThread(PRThreadBase.java:178)
at com.pega.pegarules.session.internal.mgmt.PRThreadImpl.(PRThreadImpl.java:137)
at com.pega.pegarules.session.internal.mgmt.PRThreadImpl.acquire(PRThreadImpl.java:161)
at com.pega.pegarules.session.internal.mgmt.base.RequestorThreadSync.getOrCreateThread(RequestorThreadSync.java:175)
at com.pega.pegarules.session.internal.mgmt.base.RequestorThreadSync.getOrCreateThread(RequestorThreadSync.java:162)
at com.pega.pegarules.session.internal.mgmt.base.RequestorThreadSync.getOrCreateThread(RequestorThreadSync.java:158)
at com.pega.pegarules.session.internal.mgmt.base.RequestorThreadSync.getOrCreateThread(RequestorThreadSync.java:154)
at com.pega.pegarules.session.internal.mgmt.base.RequestorThreadSync.getThread(RequestorThreadSync.java:305)
at com.pega.pegarules.session.internal.mgmt.PRRequestorImpl.getThread(PRRequestorImpl.java:777)
at com.pega.pegarules.session.internal.PRSessionProviderImpl.setProcessingThreadOnRequestor(PRSessionProviderImpl.java:1317)
at com.pega.pegarules.session.internal.PRSessionProviderImpl.doWithRequestorLocked(PRSessionProviderImpl.java:1009)
at com.pega.pegarules.session.internal.PRSessionProviderImpl.doWithRequestorLocked(PRSessionProviderImpl.java:879)
at com.pega.pegarules.session.internal.mgmt.base.NodeRequestorMgt.cleanupRequestor(NodeRequestorMgt.java:1291)
at com.pega.pegarules.session.internal.mgmt.base.NodeRequestorMgt.cleanupRequestor(NodeRequestorMgt.java:1285)
at com.pega.pegarules.session.internal.mgmt.base.NodeRequestorMgt.timeoutRequestorThrowingErrors(NodeRequestorMgt.java:1268)
at com.pega.pegarules.session.internal.mgmt.base.NodeRequestorMgt.processPassivationQueue(NodeRequestorMgt.java:2580)
at com.pega.pegarules.session.internal.async.PassivationDaemon.processPassivationQueue(PassivationDaemon.java:365)
at com.pega.pegarules.session.internal.async.PassivationDaemon.run(PassivationDaemon.java:339)
at com.pega.pegarules.session.internal.PRSessionProviderImpl.performTargetActionWithLock(PRSessionProviderImpl.java:1264)
at com.pega.pegarules.session.internal.PRSessionProviderImpl.doWithRequestorLocked(PRSessionProviderImpl.java:1013)
at com.pega.pegarules.session.internal.PRSessionProviderImpl.doWithRequestorLocked(PRSessionProviderImpl.java:833)
at com.pega.pegarules.session.internal.async.PassivationDaemon.run(PassivationDaemon.java:301)
at java.lang.Thread.run(Thread.java:745)
at (:)

***Updated by Moderator: Vidyaranjan. Removed user added #helpme and Ask the Expert tags. Apologies for confusion, shouldn't have been an end-user option*** Included SR details***

Low-Code App Development Upgrades System Administration SR Created SR Exists
Moderation Team has archived post
Share this page LinkedIn