Support Article
DataFlow with Stream dataset gets stuck at pending activation
SA-71130
Summary
A realtime dataflow has a Stream dataset as the primary source. The dataflow fails to start and is in the Pending-Activation status after to reactivating or restarting the flow. This occurs on skimming the ruleset with the Stream dataset to a higher major/minor version of the ruleset.
Error Messages
Caused by:
java.util.concurrent.ExecutionException: com.pega.dsm.dnode.api.DNodeException: There's more than one instance for dataset CC_QUEUE
at java.util.concurrent.FutureTask.report(FutureTask.java:134)
at java.util.concurrent.FutureTask.get(FutureTask.java:200)
at com.pega.dsm.dnode.impl.server.StreamDataSetRepository$1.load(StreamDataSetRepository.java:92)
... 71 more
Caused by:
com.pega.dsm.dnode.api.DNodeException: There's more than one instance for dataset CC_QUEUE
at com.pega.dsm.dnode.impl.server.StreamDataSetRepository$GetDataSetTask.isValid(StreamDataSetRepository.java:175)
at com.pega.dsm.dnode.impl.server.StreamDataSetRepository$GetDataSetTask.call(StreamDataSetRepository.java:140)
at com.pega.dsm.dnode.impl.server.StreamDataSetRepository$GetDataSetTask.call(StreamDataSetRepository.java:112)
at java.util.concurrent.FutureTask.run(FutureTask.java:274)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1157)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:627)
at com.pega.dsm.dnode.util.PrpcRunnable$1.run(PrpcRunnable.java:44)
at com.pega.dsm.dnode.util.PrpcRunnable$1.run(PrpcRunnable.java:41)
at com.pega.dsm.dnode.util.PrpcRunnable.execute(PrpcRunnable.java:52)
at com.pega.dsm.dnode.impl.prpc.PrpcThreadFactory$PrpcThread.run(PrpcThreadFactory.java:84)
Steps to Reproduce
- Log in to Designer Studio.
- Create a dataflow with Stream dataset as the source.
- Navigate to the dataflow run landing page.
- Create a realtime dataflow run.
- Activate the dataflow run. The dataflow goes to the Active status and continues to run.
- Navigate to Designer Studio > System > Refactor > Rulesets.
- Skim the ruleset that has the Stream dataset to a higher major/minor version.
- Restart the Application Server instance after skimming is complete.
- Reactivate or restart the realtime dataflow run. The run status stays in the Pending-Activation state.
Root Cause
A defect in Pegasystems’ code or rules.
According to the design, Pega can have one version of a Stream dataset instance in the system.
Resolution
Perform the below steps:
- Delete the duplicate version of the Stream dataset rule instance.
- Resave the Stream dataset instance version that must be retained in the system.
- Navigate to the System Management Application (SMA) > Advanced > Rule Cache Management.
- Delete the instance of the rule.
- Restart the Application Server.
- Open the Stream dataset rule instance and perform any operation such as browse, to initialize the Stream dataset.
Published February 22, 2019 - 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.