Support Article
VBD is too slow causing KPI visualization usage
SA-16283
Summary
In Pega 7.1.7 with Visual Business Director (VBD), user experiences extreme performance slowness and inability to effectively use KPI visualization.
Error Messages
2015-10-02 16:59:01,787 [ES PassivationDaemon] [ STANDARD] [ ] (lipboard.ReferencePropertyLink) ERROR - Cannot resolve source property for WorkPage.Customer. Link info: Is reference = true; Levels to parent = (using other named page 'NBAACustomerRef'); Relative target = .Customer; Total number of redirections = 13; Rule trace list: []; Reason: not found on source page: NBAACustomerRef
2015-10-02 16:59:01,801 [ES PassivationDaemon] [ STANDARD] [ ] (lipboard.ReferencePropertyLink) ERROR - Cannot resolve source property for WorkObjectPage.Customer. Link info: Is reference = true; Levels to parent = (using other named page 'NBAACustomerRef'); Relative target = .Customer; Total number of redirections = 3; Rule trace list: []; Reason: not found on source page: NBAACustomerRef
2015-10-02 16:59:01,816 [ES PassivationDaemon] [ STANDARD] [ ] (lipboard.ReferencePropertyLink) ERROR - Cannot resolve source property for ActionDriverWorkPage.Customer. Link info: Is reference = true; Levels to parent = (using other named page 'NBAACustomerRef'); Relative target = .Customer; Total number of redirections = 1; Rule trace list: []; Reason: not found on source page: NBAACustomerRef
2015-10-02 16:59:01,825 [ES PassivationDaemon] [ STANDARD] [ ] (lipboard.ReferencePropertyLink) ERROR - Cannot resolve source property for WorkPage.Customer. Link info: Is reference = true; Levels to parent = (using other named page 'NBAACustomerRef'); Relative target = .Customer; Total number of redirections = 13; Rule trace list: []; Reason: not found on source page: NBAACustomerRef
Steps to Reproduce
1. Logon to the Pega Application
2. Go to Designer Studio > Decisioning > Monitoring >VBD > Datasource. On this Page, click on the link "Actual”, the page is loading for longer time.
Root Cause
The issue was caused by VBD Applet refreshing too frequently. It takes about 2 seconds to perform all the queries and render the graph. By the time rendering is done, a new data is available, so user tries to refresh again. As a result Applet is constantly refreshing, preventing user from any action.
Resolution
Apply HFix-24382 to overcome the issue with VBD slowness caused due to Applet refreshing too frequently.
Published January 31, 2016 - Updated October 8, 2020
Have a question? Get answers now.
Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.