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

Poor performance loading application dashboard

SA-11353

Summary



One application is having a significant performance problem loading the dashboard when users log into the system. Response time is multi-minute, making the application virtually unusable. 

Error Messages



2015-06-08 09:50:47,077 [ WebContainer : 11] [ ] [ ] (ngineinterface.service.HttpAPI) ERROR myserver.com|xxx.x.x.x - xxx.x.x.x: com.pega.pegarules.pub.context.RequestorLockException
com.pega.pegarules.pub.context.RequestorLockException: Unable to synchronize on requestor H01BC0CDB57C67B62159C084791C8AD64 within 120 seconds: (thisThread = WebContainer : 11) (originally locked by = WebContainer : 50) (finally locked by = WebContainer : 50)

at com.pega.pegarules.session.internal.PRSessionProviderImpl.doWithRequestorLocked(PRSessionProviderImpl.java:988)
at com.pega.pegarules.session.internal.PRSessionProviderImpl.doWithRequestorLocked(PRSessionProviderImpl.java:776)
at com.pega.pegarules.session.external.engineinterface.service.EngineAPI.processRequest(EngineAPI.java:324)
at com.pega.pegarules.session.internal.engineinterface.service.HttpAPI.invoke(HttpAPI.java:676)
at com.pega.pegarules.session.internal.engineinterface.etier.impl.EngineImpl._invokeEngine_privact(EngineImpl.java:312)
at com.pega.pegarules.session.internal.engineinterface.etier.impl.EngineImpl.invokeEngine(EngineImpl.java:263)
at com.pega.pegarules.session.internal.engineinterface.etier.ejb.EngineBean.invokeEngine(EngineBean.java:236)


Steps to Reproduce



Log in to the application and time how long it takes the dashboard to load.

Root Cause



The root cause of this problem is defect/misconfiguration in the operating environment.

Resolution



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

Oracle database statistics were regenerated and were no longer pinned for a set of work tables accessed during login and the display of the user dashboard. Re-pin the table statistics to allow the Oracle query optimizer to use indexes correctly and restore normal performance. 
Suggest Edit

Published July 2, 2015 - Updated October 8, 2020

Did you find this content helpful? Yes No

100% found this useful

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