Unable to queue record for 5 minutes for processing in data flow

Hi All,

While running the multiple campaigns we are observing the below error in logs

ERROR : Unable to queue record for 5 minutes for processing in data flow. Retrying

Solutions Attempted:

We performed the following change to the operating environment to utilize the better performing /dev/urandom:Update the JVM settings to include the below

But still we are observing the error in logs , which leads to delay in campaign execution during campaign . I am also attaching the PegaRULES.log and PegaRULES-ALERT.log for reference.


Keep up to date on this post and subscribe to comments

September 17, 2019 - 2:47pm

In the dataflows, what warnings do you see? Also, what is your app server? If tomcat, share the context.xml.

September 20, 2019 - 6:12am
Response to KevinZheng_GCS

Hi Kevin,

We are using Oracle weblogic application server 12c version.



September 18, 2019 - 4:30am

What is your Pega Version? 

September 20, 2019 - 5:59am
Response to roya2_gcs

We are using Pega 7.3.1 version

September 20, 2019 - 6:44am

So, that brings us back to Kevin's question about what warnings are seen in the Dataflows. Please refer to the following link - particularly the section on "Viewing the error count per component". This will show us what Pega sees as the cause of the issue.

Your log is also showing DBMS issues -  ConnectionDeadSQLExceptions from a connection pool that Pega is referencing in the WebLogic container. Perhaps this database was restarted ... would need to see how the data source is set up. The issue you have is likely a symptom.

Your environment continues to encounter errors as a direct result of the database issue over the entire day.  Restarting the JVM will address the issue - Pega relies on the database to load java classes, and downtime at the database level that is not handled via failover can and will cause the environment to behave unpredictably and cause significant instability.