Support Article
Data flows landing page keep loading and cause hang
SA-64829
Summary
Post upgrade, the system crashes frequently when accessing the Batch Data Flow landing page.
Error Messages
[PegaRULES-Batch-3] [STANDARD] [ ] [APP1:01.01.01] (flow.service.DataFlowRunConfig) ERROR - Cannot get the dataflow [Pega-xyz-MYAPP-Data-Person-SEG<Seg name>.DFPRTest671] defined by this configuration. Will assume it's neither resumable nor stream for the resilience configuration
com.pega.dsm.dnode.api.DNodeException: Can't open dataflow ABC-XYZ-ELMAKO-Data-Person-SEGMBB3Gto4GUpdV2.DFPRTest671 - doesn't exist
at com.pega.dsm.dnode.api.dataflow.DataFlows.dataFlowNotFoundException(DataFlows.java:138) ~[dnode-7.4.0.jar:?]
at com.pega.dsm.dnode.api.dataflow.DataFlows.instance(DataFlows.java:88) ~[dnode-7.4.0.jar:?]
at com.pega.dsm.dnode.impl.dataflow.service.RuleBasedDataFlowFactory.newInstance(RuleBasedDataFlowFactory.java:20) ~[dnode-7.4.0.jar:?]
at com.pega.dsm.dnode.api.dataflow.service.DataFlowRunConfig$1.run(DataFlowRunConfig.java:434) ~[dnode-7.4.0.jar:?]
at com.pega.dsm.dnode.api.dataflow.service.DataFlowRunConfig$1.run(DataFlowRunConfig.java:431) ~[dnode-7.4.0.jar:?]
at com.pega.dsm.dnode.util.PrpcRunnable.execute(PrpcRunnable.java:52) ~[dnode-7.4.0.jar:?]
at com.pega.dsm.dnode.impl.prpc.service.ServiceHelper$3.run(ServiceHelper.java:219) ~[dnode-7.4.0.jar:?]
at com.pega.pegarules.session.internal.PRSessionProviderImpl.performTargetActionWithLock(PRSessionProviderImpl.java:1357) ~[prprivate.jar:?]
at com.pega.pegarules.session.internal.PRSessionProviderImpl.doWithRequestorLocked(PRSessionProviderImpl.java:1105) ~[prprivate.jar:?]
at com.pega.pegarules.session.internal.PRSessionProviderImpl.doWithRequestorLocked(PRSessionProviderImpl.java:912) ~[prprivate.jar:?]
at com.pega.dsm.dnode.impl.prpc.service.ServiceHelper.executeInPrpcContextInternal(ServiceHelper.java:212) ~[dnode-7.4.0.jar:?]
at com.pega.dsm.dnode.impl.prpc.service.ServiceHelper.executeInPrpcContext(ServiceHelper.java:104) ~[dnode-7.4.0.jar:?]
at com.pega.dsm.dnode.api.dataflow.service.DataFlowRunConfig.getDataFlow(DataFlowRunConfig.java:431) ~[dnode-7.4.0.jar:?]
at com.pega.dsm.dnode.api.dataflow.service.DataFlowRunConfig.getResilienceConfig(DataFlowRunConfig.java:294) ~[dnode-7.4.0.jar:?]
at com.pega.dsm.dnode.api.dataflow.service.DataFlowRunConfig.getServiceInstanceName(DataFlowRunConfig.java:137) ~[dnode-7.4.0.jar:?]
at com.pega.dsm.dnode.api.dataflow.service.DataFlowRunConfig.<init>(DataFlowRunConfig.java:129) ~[dnode-7.4.0.jar:?]
at com.pega.dsm.dnode.api.dataflow.service.DataFlowRunConfig.from(DataFlowRunConfig.java:218) ~[dnode-7.4.0.jar:?]
at com.pega.dsm.dnode.impl.dataflow.model.WorkObject.getRunConfig(WorkObject.java:76) ~[dnode-7.4.0.jar:?]
at com.pega.dsm.dnode.impl.dataflow.service.persistence.db.RunDbPersistence$6.apply(RunDbPersistence.java:263) ~[dnode-7.4.0.jar:?]
at com.pega.dsm.dnode.impl.dataflow.service.persistence.db.RunDbPersistence$6.apply(RunDbPersistence.java:260) ~[dnode-7.4.0.jar:?]
at com.pega.dsm.dnode.api.stream.DataOperator$2$1.onNext(DataOperator.java:35) ~[dnode-7.4.0.jar:?]
at com.pega.dsm.dnode.impl.stream.DataObservableImpl$SafeDataSubscriber.onNext(DataObservableImpl.java:290) ~[dnode-7.4.0.jar:?]
.
.
.
com.pega.dsm.dnode.api.dataflow.service.DataFlowRunFactory.getByType(DataFlowRunFactory.java:98) ~[dnode-7.4.0.jar:?]
at com.pega.dsm.dnode.impl.dataflow.service.DataFlowServiceImpl.getByType(DataFlowServiceImpl.java:510) ~[dnode-7.4.0.jar:?]
at com.pega.dsm.dnode.impl.dataflow.service.DataFlowServiceProxy.getByType(DataFlowServiceProxy.java:295) ~[dnode-7.4.0.jar:?]
at com.pega.dsm.dnode.impl.dataflow.activity.LoadRunsForLandingPage.pzGetTheRuns(LoadRunsForLandingPage.java:31) ~[dnode-7.4.0.jar:?]
at com.pegarules.generated.activity.ra_action_pzloadruns_4c22ca314a9a485554f363cf8ab21500.step1_circum0(ra_action_pzloadruns_4c22ca314a9a485554f363cf8ab21500.java:159) ~[?:?]
at com.pegarules.generated.activity.ra_action_pzloadruns_4c22ca314a9a485554f363cf8ab21500.perform(ra_action_pzloadruns_4c22ca314a9a485554f363cf8ab21500.java:70) ~[?:?]
Steps to Reproduce
- Log in to Designer Studio.
- Navigate to Decisioning > Decisions > Data Flows > Batch Processing.
Root Cause
A defect in Pegasystems’ code or rules.
Loading multiple data flow runs caused the block in thread processing.
Resolution
Apply HFix-46791.
Run Data-Decision-Service pyDeleteByStatusAndTime activity to delete failed and old data flow run items to reduce the amount of entries.
Published October 6, 2018 - Updated December 2, 2021
Have a question? Get answers now.
Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.