Question
Coforge DPA private limited
AU
Last activity: 20 Jul 2020 3:11 EDT
Queue processor issue- items are stuck at schedule task list
Hi,
Items are getting queued to Queue processor which are showing at "Scheduled" column but when the schedule time arrives it is still showing in the Scheduled list, it is not moving to "Ready to process". any suggestion is appreciated. Its a pre production issue.
-
Like (0)
-
Share this page Facebook Twitter LinkedIn Email Copying... Copied!
Pegasystems Inc.
FR
Hello,
What Pega version is it? Can you try to open up one of those instances to check the content an error in there or on your logs during processing.
Coforge DPA private limited
AU
I am using Pega 821 version. there is no error. it is just that item is present in Scheduled task and not moving from there. QP activity will be triggered when item is in the Ready to process but it is not even going into that.
Pegasystems Inc.
US
check if the stream service is running, also check the related dataflow for your QP (from Admin Studio).
JP Morgan Chase
US
I am also facing the same above issue.Found any root cause?
Pegasystems Inc.
IN
Hi,
Thank you for posting your query in the PSC. This looks like an inactive post and hence, we suggest you create a new post for your query. Click on the Write Post button here. Once created, please reply here with the URL of the new post.
You may also refer this discussion link as a reference in the new thread.
Bank of America
IN
If you use Queueporcessor, please make sure you have at least one node classified as “Backgroundprocessing”. Since there is job scheduler “pzDelayedQueueProcessorSchedule” is responsible to for reading scheduled Queprocessor messages and sending them to KAFKA stream service. As this is a system default JS and was configured to run on Backgroundprocessing node type you can’t change it.
Without having Backgroundprocessing node, QP will not work in Delayed mode or can’t do multiple attempts in locking scenario. Attached is the SR gives the resolution.
-
Karan Narvani
Incessant Technologies Pvt.Ltd
AU
Hi MadhuSudhan,
Following might be the reasons for the items not being moved from scheduled to Read To Process.
1. If the Queued Page size is more than 5 MB then the items wont move. For this always try to keep the page size less. There is a configuration which you can configure for increasing the size of the Page but it is not recommended.
2. When ever the Queue item is picked up for processing if the partition information from Kafka is not available then also the items will be stuck.
Regards,
Chaitanya.
Singtel Optus
AU
Hi,
I am having scenario, where 'System-Queue-DefaultEntry' is getting piled up in "Scheduled" queue but still notifications where acknowledged to the customer and still Instances are queued under "Scheduled" and it is not moving to "Success" queue.
Updated: 20 Jul 2020 3:10 EDT
Bank of America
IN
If you use Queueporcessor, please make sure you have at least one node classified as “Backgroundprocessing”. Since there is job scheduler “pzDelayedQueueProcessorSchedule” is responsible to for reading scheduled Queprocessor messages and sending them to KAFKA stream service. As this is a system default JS and was configured to run on Backgroundprocessing node type you can’t change it.
Without having Backgroundprocessing node, QP will not work in Delayed mode or can’t do multiple attempts in locking scenario. Attached is the SR gives the resolution.
-
George Jacob Indrajit Gorai