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

Unable to synchronize on requestor in AES report

SA-16548

Summary



User is unable to synchronize on requestor in AES report


Error Messages

Type com.pega.pegarules.pub.context.RequestorLockException
Message Unable to synchronize on requestor H33C0D659C3FF9B15103B759C6F89888C within 120 seconds: (thisThread = http-/127.0.0.1:8080-9) (originally locked by = http-/127.0.0.1:8080-8) (finally locked by = http-/127.0.0.1:8080-8)


Unable to synchronize on requestor H33C0D659C3FF9B15103B759C6F89888C within 120 seconds: (thisThread = http-/127.0.0.1:8080-9) (originally locked by = http-/127.0.0.1:8080-8) (finally locked by = http-/127.0.0.1:8080-8)
Exception Class com.pega.pegarules.pub.context.RequestorLockException


Steps to Reproduce



Not Applicable


Root Cause



While using a report definition 'my_custom_report', data retrieval is taking long time due to high volume of records in the database.
Also, user is using 'Export to Excel ' functionality in report definition for exporting the data, which is causing high interaction time as HTTP interation alerts are observed in the alerts file.

Resolution



As report definiton is causing this issue, user is advised to fine tune the  database table consisting of high volume of records and a high execution plan. Below recommendations are advised to speed up the execution.

1. Create Indexing on the columns which are involved in the query.
2. Create materialised views to retrieve data specific to a time period, which is used on a daily basis, thus reducing the number of records being traversed before returning the results.
3. Use periodic database table backup to avoid high number of records in the table.
4. Tune the query to eliminate duplicate recorrds and use additional criteria to reduce the fetch size.

 

 

Published February 9, 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