Skip to main content

This content is closed to future replies and is no longer being maintained or updated.
Links may no longer function. If you have a similar request, please write a new post.

Question

 Hemant Kumar (HemantK1)
Wells Fargo

Wells Fargo
IN
HemantK1 Member since 2021 1 post
Wells Fargo
Posted: Oct 5, 2021
Last activity: Sep 16, 2022
Posted: 5 Oct 2021 8:15 EDT
Last activity: 16 Sep 2022 11:58 EDT
Closed

Queue Processor not processing scheduled items

Hi all,

I am facing issue in UAT environment where I am queuing items in queue processor via an email listener. But the queued items are not getting processed. But the same queue processor is working fine in lower environments i.e. Dev and SIT. The items remains in scheduled state without getting into ready for process or broken stage.

Also, I have checked the stream node and it is working fine, checked the PegaRules log and seeing no issues related to queue processor.

 

So, related to it, can you please suggest what I can check to resolve this issue?

 

Thanks,

Hemant 

***Edited by Moderator Marissa to update Capability tags****
To see attachments, please log in.
Pega Platform 8.4
System Administration
Financial Services
Senior System Architect

  • Mert Çaldağ
Posted: 3 years ago
Posted: 5 Oct 2021 8:48 EDT
Hemant Kumar (HemantK1)
Wells Fargo

Wells Fargo
IN

@HemantK1 : FYI, as an update, I have found that pzDelayedQueueProcessorSchedule Job scheduler is not working which makes the delayed queue processor items to ready to process. But I still need to know why this Job scheduler is not working. This Pega OOTB job scheduler.

 

I really appreciate if anyone shares their inputs

 

Thanks,

Hemant

To see attachments, please log in.
Posted: 2 years ago
Posted: 31 Jan 2022 4:34 EST
Mert Çaldağ (m.caldag)
Bentego
Pega Senior System Architect
Bentego
TR

@HemantK1  we are facing literally the same issue. However, when i check the "Enable Job Scheduler" option after opening the rule instance of job scheduler one of the production node, it seems enabled.  

How did you identify pzDelayedQueueProcessorSchedule job scheduler rule not working on production? It was not enabled or something else? Is there any configuration on admin studio?

To see attachments, please log in.
Posted: 2 years ago
Posted: 16 Sep 2022 11:58 EDT
alphonse vivanloc (alphonsev)
Capgemini Service

Capgemini Service
FR

@HemantK1 we faced same issue delayed QP was stuck for only one environment but others environment are OK.

and pzDelayedQueueProcessorSchedule  were disabled everywhere.

i opened a INC and resolved it with that support answer:

Issue

QP messages are not moving from the Scheduled Status.

Analysis

  1. In 8.6 by default, DelayedItemsDataFlowService DF is responsible to move the messages from Scheduled status.
  2. In defect environment, queueprocessor/delayeditems/dataflowbased/enabled DSS was not configured which means DelayedItemsDataFlowService should be responsible to move the records.
  3. When we try to open the Pega-DM-DDF-Work. DelayedItemsDataFlowService DF, getting following error message java.lang.IllegalStateException: Loaded a work object [DelayedItemsDataFlowService] while no run config was present.
  4. Data-Decision-DDF-RunOptions.DelayedItemsDataFlowService Instance was not present in the environment.
  5. When we verify in working environments, Data-Decision-DDF-RunOptions.DelayedItemsDataFlowService instance was present

Next Steps:

Client to implement following things

Show More

@HemantK1 we faced same issue delayed QP was stuck for only one environment but others environment are OK.

and pzDelayedQueueProcessorSchedule  were disabled everywhere.

i opened a INC and resolved it with that support answer:

Issue

QP messages are not moving from the Scheduled Status.

Analysis

  1. In 8.6 by default, DelayedItemsDataFlowService DF is responsible to move the messages from Scheduled status.
  2. In defect environment, queueprocessor/delayeditems/dataflowbased/enabled DSS was not configured which means DelayedItemsDataFlowService should be responsible to move the records.
  3. When we try to open the Pega-DM-DDF-Work. DelayedItemsDataFlowService DF, getting following error message java.lang.IllegalStateException: Loaded a work object [DelayedItemsDataFlowService] while no run config was present.
  4. Data-Decision-DDF-RunOptions.DelayedItemsDataFlowService Instance was not present in the environment.
  5. When we verify in working environments, Data-Decision-DDF-RunOptions.DelayedItemsDataFlowService instance was present

Next Steps:

Client to implement following things

  1. Package(RAP) the Data-Decision-DDF-RunOptions DelayedItemsDataFlowService Instance in working environment and install the package in defect environment.
  2. Open the Pega-DM-DDF-Work. DelayedItemsDataFlowService DF and check the status of DF run. If it is in-progress then DF would process the messages. If not, try to start the DF run.
  3. Monitor whether messages are moving from scheduled status or not

 

 

Show Less
To see attachments, please log in.
Posted: 2 years ago
Posted: 31 Jan 2022 6:25 EST
Mohammed Arshad Pasha (ArshadPashaMohammed)
Aaseya IT services Pvt Ltd
Lead system architect
Aaseya IT services Pvt Ltd
SA

@HemantK1

Make sure Stream node is up and in normal state , for queue processor to pick the messages from topic .

To start the stream if other than normal state , you can go to actions and select Start as an action as attached here.

Else , you can try for restarting the server notifying your codevelopers about restart.

you can refer the below link for more details

https://docs-previous.pega.com/system-administration/84/queue-processor-rules

 

To see attachments, please log in.

We'd prefer it if you saw us at our best.

Pega Collaboration Center 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