Errors while performing requestor quiesce : Requestor no longer valid, processing not possible.
Below mentioned error messages has been observed in the logs and are severely causing performance test login failure issues.
1) ][error while performing requestor quiesce][STACK][com.pega.pegarules.pub.context.RequestorLockException: Requestor no longer valid, processing not possible.
2)Exception: PRSecurity Exception occured:
Refer to the attachment for the above mentioned exceptions related error stacks.
***Moderator Edit-Vidyaranjan: Updated SR details***
Keep up to date on this post and subscribe to comments
- Requirement-I have a drill down report definition where I can view it in report browser. But when I see it in the section, it is not possible.
- Login to Pega not possible. please assist asap.
- How to check if a date format is valid, in an activity?
- SAML SSO: Error Message: Unable to process the SAML Web SSO request: Unable to process SAML2 Authentication response: Caught Exception while validating SAML2 Authentication response protocol: NULL
- We are performing an automatic JVM refresh on a nightly basis. Is there a way to automate or schedule quiescing?