Nack and requeue, quorum queue delivery limit and messages order

[florent maillard]

Hello,

I'm using RabbitMQ 3.8.9 with protocol AMQP 0.9.1. My test have been done with both Python implementation : pika and java-client in last version.

Context

I created a quorum queue with a delivery limit policy of 1. Messages are sent to a dead letter queue after this only retry

Only one consumer will be used

A prefetch count of 1 is configured 

How I proceed

I create a connection and the a channel. I basic_consume the queue and nack every message I receive with a requeue. So they all go to the dead letter queue after one retry

I publish 9 messages to the queue with a simplistic payload : A number from 1 to 9

What I expect 

To obtain messages in this order (and 2 times due to the reply policy) : 112233445566778899

What I obtain

As you can see the first one is correct.

Then I receive 2 messages in a row (2 and 3)

And after 4 messages (4, 5, 6 and 7)

... You know the mathematical sequence. It doubles each time

What am I missing ? How can you explain this behavior ?

Regards,

Florent

[kjnilsson]

3.8 is pretty old, please can you try this against the latest version and let us know if there is still anything to discuss. 

Cheers

Karl

[florent maillard]

Thanks kjnilsson,

I will ask my OPS colleagues to do so and I will come back later

Regards

[florent maillard]

Hello Kjnilsson,

I implemented on my own a rabbitMQ instance on docker (way faster than my company).
Still same issue and same behavior in v 3.10.7

Regards,

Florent

--
You received this message because you are subscribed to a topic in the Google Groups "rabbitmq-users" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/rabbitmq-users/iMcX0oXzURQ/unsubscribe.
To unsubscribe from this group and all its topics, send an email to rabbitmq-user...@googlegroups.com.
To view this discussion on the web, visit https://groups.google.com/d/msgid/rabbitmq-users/bdda37a2-fe32-4747-a117-bc810a0c63c3n%40googlegroups.com.

[Michal Kuratczyk]

Hi,

Please publish your test app to a git repo so we can use it for reproducing the problem.

Thanks,

You received this message because you are subscribed to the Google Groups "rabbitmq-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to rabbitmq-user...@googlegroups.com.
To view this discussion on the web, visit https://groups.google.com/d/msgid/rabbitmq-users/CAEqa5FVhyUsLbg3Go%3DH%3D1Zw7a8oiSeDPmvbdKBQ2xqeCbM73gA%40mail.gmail.com.

--

Michał

RabbitMQ team

[florent maillard]

Hi Michal,

The public git repo is available there : https://gitlab.com/sandboxFMA/rabbitmq-issue

Sorry for the delay, I'm currently on vacation

Regards,

Florent Maillard

To view this discussion on the web, visit https://groups.google.com/d/msgid/rabbitmq-users/CAA81d0u-WGd09eyc0BqZm6p6wQFe7RNR9NMhD1P%2BMiA9CGVcvw%40mail.gmail.com.

[david....@gmx.de]

Thank you Florent for reporting this issue and the great repro steps.

It's a bug in RabbitMQ and gets fixed by https://github.com/rabbitmq/rabbitmq-server/pull/5609

[florent maillard]

Thanks a lot for your answer

I will be able to correct 😁

Regards,

Florent 

To view this discussion on the web, visit https://groups.google.com/d/msgid/rabbitmq-users/e709baca-3c0b-410c-8cef-7f8d078de30fn%40googlegroups.com.