Queries around retry mechanism and dead letter queue.

[utkarsh19467]

Hi Team,

1. When we tried method enqueueWithRetry with retryCount as 3 and throwing an exception from listeners, so according to doc it should go to dead letter queue but we encountered an error "Queue Config not found for queue DeadLetterQueue(name=failed-delay-queue, consumerEnabled=true)". Can you suggest here what are we missing.

2. After enqueueWithRetry our message is moved to dead letter queue, but on UI size of Dead is showing as -1 and also it is not consumed by the listener even though we specified "deadLetterQueueListenerEnabled"="true" . When we used utility to move message from Dead Letter Queue to Main queue, messages are lost and we were not able to see anywhere. Can you please explain this scenario.

3. Does Rqueue supports telegram alerting integration if a message/task is moved to dead letter queue. We want rqueue to raise an alert to one of our telegram group. Is this integration possible.

4. We created a listener with dead letter queue specified but we didn't mentioned "deadLetterQueueListenerEnabled"="true". Now we enqueued one message for a delay of 60 seconds and stopped our application so that message should go in dead letter queue. Now after 2 minutes if we start our application, as per doc we should see our message in dead letter queue but we saw that it is consumed and logged in our application. Even though "deadLetterQueueListenerEnabled" is false we are getting message consumed. Can you please suggest why this is happening.

5. We can see a jobs tab in scheduled messages. How those jobs are created, can you please explain the flow for this. We were trying to execute API /rqueue/api/v1/jobs with messageId. So, for scheduled messages we found "no jobs found" error but for message that encountered exception we were able to see data from API. Can you please help to understand this usecase.

Regards

[sonus21]

• When we tried method enqueueWithRetry with retryCount as 3 and throwing an exception from listeners, so according to doc it should go to dead letter queue but we encountered an error "Queue Config not found for queue DeadLetterQueue(name=failed-delay-queue, consumerEnabled=true)". Can you suggest here what are we missing.
• After enqueueWithRetry our message is moved to dead letter queue, but on UI size of Dead is showing as -1 and also it is not consumed by the listener even though we specified "deadLetterQueueListenerEnabled"="true" . When we used utility to move message from Dead Letter Queue to Main queue, messages are lost and we were not able to see anywhere. Can you please explain this scenario.

You've configured Rqueue to consume events from dead letter queue, but you've not attached any listeners on this queue.

Basically you need to configure one additional listener to consume event from dead letter queue.

rqueue/rqueue-spring-common-test/src/main/java/com/github/sonus21/rqueue/test/MessageListener.java

Line 218 in 2fdbbe7

public void onMessageReservationRequest(ReservationRequest request) throws Exception {

rqueue/rqueue-spring-common-test/src/main/java/com/github/sonus21/rqueue/test/MessageListener.java

Line 230 in 2fdbbe7

public void onMessageReservationRequestDeadLetterQueue(

• Does Rqueue supports telegram alerting integration if a message/task is moved to dead letter queue. We want rqueue to raise an alert to one of our telegram group. Is this integration possible.

I think you've not gone through wiki. You can add message processor, please go through wiki

https://github.com/sonus21/rqueue/wiki/Callback-Events

• We created a listener with dead letter queue specified but we didn't mentioned "deadLetterQueueListenerEnabled"="true". Now we enqueued one message for a delay of 60 seconds and stopped our application so that message should go in dead letter queue. Now after 2 minutes if we start our application, as per doc we should see our message in dead letter queue but we saw that it is consumed and logged in our application. Even though "deadLetterQueueListenerEnabled" is false we are getting message consumed. Can you please suggest why this is happening.

I think you've misunderstood about dead letter queue. Messages would be moved to dead letter queue only after all retries are over.

• We can see a jobs tab in scheduled messages. How those jobs are created, can you please explain the flow for this. We were trying to execute API /rqueue/api/v1/jobs with messageId. So, for scheduled messages we found "no jobs found" error but for message that encountered exception we were able to see data from API. Can you please help to understand this usecase.

Scheduled jobs are created automatically in three cases

• When you insert a periodic job
• when you insert a job with delay
• when a job is failed and it has to be retried.

Please go through following links:

• https://github.com/sonus21/rqueue/wiki
• https://sonus21.medium.com/introducing-rqueue-redis-queue-d344f5c36e1b