Question
Virtusa Corportaion
US
Last activity: 14 Sep 2016 11:43 EDT
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.
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 | |||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
***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***
Accepted Solution
Pegasystems Inc.
US
Virtusa Corportaion
US
Submitted additional SR SR-A95705
Accepted Solution
Pegasystems Inc.
US
Not much can be determined without some context of what is failing to be activated and what platform you are on. The com.pega.pegarules.pub.PRRuntimeException typically has a caused by in the logs. That could be helpful.
A good logger for debugging issues like this is "com.pega.TRACE.requestor_lifecycle". Set this to DEBUG. But, be careful...it is an active logger. I'd only have it in place as long as you need to get a capture of the incident AS WELL AS capturing the activity for the 30 miunutes or so on the particular requestor showing the issue.
Is this perhaps a multi-tenant deployment? "Legacy context" is typically mentioned in conjunction with Application Context.
Virtusa Corportaion
US
Errors disapated without any changes on our side.
Not much can be determined without some context of what is failing to be activated and what platform you are on. The com.pega.pegarules.pub.PRRuntimeException typically has a caused by in the logs. That could be helpful.
A good logger for debugging issues like this is "com.pega.TRACE.requestor_lifecycle". Set this to DEBUG. But, be careful...it is an active logger. I'd only have it in place as long as you need to get a capture of the incident AS WELL AS capturing the activity for the 30 miunutes or so on the particular requestor showing the issue.
Is this perhaps a multi-tenant deployment? "Legacy context" is typically mentioned in conjunction with Application Context.