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

Campaign failure, timeout whilst waiting for data flow

SA-31665

Summary



A campaign failed with an error saying that the configured timeout whilst waiting for a single row had been reached.
Looking at the logs there are multiple assing-ddf failures on the node.

​User sees that the data flow completed and processed all the data they were expecting.

This error has only appeared on this campaign.


Error Messages


Reached configured timeout whilst processing a single row.

2016-11-29 18:33:32,244 [p: [AAMKT:Technical]] [ STANDARD] [ ] [ ] ( dataflow.manager.LocalRun) ERROR - Problem running assignment[ASSIGN-DDF PR-210!DIST50], moving to next
com.pega.dsm.dnode.api.DNodeException: Error trying to generate dataflow <Data Flow Name>.DF8a6a129fff5c6d81e7716df30660688b58804420
at com.pega.dsm.dnode.api.dataflow.DataFlows.instance(DataFlows.java:80)
at com.pega.dsm.dnode.impl.dataflow.manager.LocalRun.execute(LocalRun.java:148)
at com.pega.dsm.dnode.impl.dataflow.manager.LocalRun.lockAndRun(LocalRun.java:87)
at com.pega.dsm.dnode.impl.dataflow.manager.LocalRun.run(LocalRun.java:63)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at com.pega.dsm.dnode.impl.prpc.PrpcThreadFactory$PrpcThread.run(PrpcThreadFactory.java:81)
Caused by: com.pega.dsm.dnode.api.DNodeException: Can't open dataflow AA-FW-Data-Customer-SEGJeganNewsletterMini.DF8a6a129fff5c6d81e7716df30660688b58804420 - doesn't exist
at com.pega.dsm.dnode.api.dataflow.DataFlows.dataFlowNotFoundException(DataFlows.java:114)
at com.pega.dsm.dnode.api.dataflow.DataFlows.loadDataFlow(DataFlows.java:105)
at com.pega.dsm.dnode.api.dataflow.DataFlows.instance(DataFlows.java:74)
... 6 more

Repeated 98 times on the 173v node starting at 18:33:32


Steps to Reproduce



Run a campaign.


Root Cause



The seed generation used by the Pega Security takes a lot of time on a Linux environment.

Resolution



On Linux systems following jvm argument is required to use urandom instead of random (random is very slow compare to urandom):

-Djava.security.egd=file:/dev/./urandom

Published August 23, 2017 - Updated December 2, 2021

Was this useful?

0% found this useful

Have a question? Get answers now.

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

Did you find this content helpful?

Want to help us improve this content?

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