Lately I am seeing this issue on our Dev system which has a single node configured as Stream, BackgroundProcessing. I created a dedicated queue processor and after processing some 1000 records it just went into Pause state. All queued items are showing up under Ready To Process and are not moving from there. When I checked the Data Flow it is showing state as "Pausing" and 100 warnings for stale threads detected. There was no failure and all 1000 records processed successfully.
When I tried to stop the queue it's throwing an error "Queue processor, <> couldn't reach a stable state. Please check after some time." I have no idea on how much time I can wait as this is in this state since yesterday. I checked the Stream service too and it's in Normal status with Action as Execute. Could some one please help me what might be the cause and how to prevent this happening in future? Will this be a severe issue on Production?
***Edited by Moderator: Pooja Gadige to add capability tag***
@Will Cho We raised an SR with Pega support and they are still looking into this. Yesterday we had a meeting with Pega support team and shared the documents and logs with them. I will let you know once we get a resolution from them.
Meanwhile I tried using the "None" option for "Lock using" and it looks like working without any issue. The queue never went down till now and it's fast too. So, you can try using "None" option with "Queue current snapshot of page" option in the Queue-For-Processing method configuration and see how it is working. I didn't enable "Queue current snapshot of page" till now but you can toggle this option and see how it performs. With this option enabled it should gain even more performance.