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

ADM Update Reporting Data slow refresh and thread dump in logs

SA-24034

Summary



After clicking on the "Update Reporting Data" button in the "Decisioning: Adaptive Model Reporting", it takes an average of 12 minutes for the data to refresh.
Clicking the "Update Reporting Data" button repeatedly can sometimes throw “Unable to synchronize on requestor” error trace in the log file.

Error Messages



On the UI:

There has been an issue; please consult your system administrator
Tue May 03 12:41:57 BST 2016


In the log file: Thread dump was generated and immediate followed by "unable to synchronize" error -

2016-05-03 12:41:57,755 [ WebContainer : 9] [ ] [ ] [ ] (.timers.EnvironmentDiagnostics) INFO - --- Thread Dump Starts ---

--- Thread Dump Complete ---
2016-05-03 12:41:57,755 [ WebContainer : 9] [ ] [ ] [ ] (ngineinterface.service.HttpAPI) ERROR : com.pega.pegarules.pub.context.RequestorLockException
com.pega.pegarules.pub.context.RequestorLockException: Unable to synchronize on requestor H3D051FB171288EE1FA53C1EAEC78B1BF within 120 seconds: (thisThread = WebContainer : 9) (originally locked by = WebContainer : 12) (finally locked by = WebContainer : 12)


Steps to Reproduce



Click on the "Update Reporting Data" button in the "Decisioning: Adaptive Model Reporting" Page.


Root Cause



The “ADMSnapshot” Agent is running without any issues, which can be verified by logging into the System Management Application.

This would enable update of ADM reporting data at scheduled intervals. To avoid duplicate snapshots, one must make sure there is only one node enabled to run the ADMSnapshot Agent when working in a multi-node Pega7 environment.

For more details refer DSM installation guide, Page# 31.


Resolution



Adjust the Batch size by changing the admmart or batchSize Dynamic System Setting in the Pega-ProcessCommander Ruleset.

Batch size for taking a snapshot is 50, by default; a value considered suitable even in cases of large size models.

Suggest Edit

Published June 16, 2016 - Updated October 8, 2020

Did you find this content helpful? Yes No

Have a question? Get answers now.

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

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