Unable to synchronize on requestor in AES report
User is unable to synchronize on requestor in AES report
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
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.
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
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.