Skip to main content

This content has been archived and is no longer being updated. Links may not function; however, this content may be relevant to outdated versions of the product.

Support Article

Performance issues and Requestorlock exceptions

SA-9237

Summary

  • The Application Explorer and Data Explorer do not work in the Designer Studio.
  • The Guardrail warnings do not load.
  • PEGA0005 alerts are observed in the logs.

Error Messages



2015-04-14 15:03:23,017 [http-bio-8080-exec-8] [TABTHREAD1] [ ] [ HSE:01.01.01] (ngineinterface.service.HttpAPI) ERROR your_url.com|your_ip your_operatorid- your_ip: com.pega.pegarules.pub.PRRuntimeError
com.pega.pegarules.pub.PRRuntimeError: PRRuntimeError
at com.pega.pegarules.session.internal.mgmt.base.ThreadRunner.runActivitiesAlt(ThreadRunner.java:707)
at com.pega.pegarules.session.internal.mgmt.PRThreadImpl.runActivitiesAlt(PRThreadImpl.java:435)

2015-04-14 15:14:45,212 [ttp-bio-8080-exec-14] [ ] [ ] [ ] (ngineinterface.service.HttpAPI) ERROR
your_url.com|your_ip your_operatorid- your_ip: com.pega.pegarules.pub.context.RequestorLockException
com.pega.pegarules.pub.context.RequestorLockException: Unable to synchronize on requestor HA3DEFCC522924AF76FBC8F559667D69C within 120 seconds: (thisThread = http-bio-8080-exec-14) (originally locked by = http-bio-8080-exec-8) (finally locked by = http-bio-8080-exec-8)


Steps to Reproduce

  1. Log in to Pega using default credentials.
  2. Load the Application Explorer and Data Explorer.

Root Cause



The root cause of this problem is an updated DB index, database config settings, and a Pega Dynamic System Setting which affects DB interactions.


Resolution



This issue is resolved by making the following change to the operating environment: 

1. Set the following Data Admin System Setting:


<env name="reporting/useLayerCakeSchemaChanges" value="true"/>

2. Set the following in the postgres.conf

"checkpoint_completion_target";"0.7" ->increase to "0.9"
"checkpoint_segments";"8"-> increase to "32"
  • Spread out or speedup checkpoint exam
"random_page_cost";"4"-> decrease to "1" (in favor of index scan)

3. Add or update the following DB index:

prpc=# Create index pr_index_warnings_idx1 on pegarules.pr_index_warnings 
prpc-# ( 
prpc(# pxReferencingRuleInsKey, 
prpc(# pxObjClass, 
prpc(# pxWarningCreatedTime, 
prpc(# pxWarningCreateOperator, 
prpc(# pxWarningSeverity 
prpc(# ); 
CREATE INDEX 
prpc=# 

prpc=# vacuum analyze pegarules.pr_index_warnings; 
VACUUM

Published January 31, 2016 - Updated October 8, 2020

Was this useful?

0% found this useful

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

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

Pega Community 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
Contact us