Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

A model shutdown occurs if the consumer does not acknowledge the received message in 15 minutes #3032

Closed
Kalhorn opened this issue May 11, 2021 · 1 comment
Labels

Comments

@Kalhorn
Copy link

Kalhorn commented May 11, 2021

Rabbit MQ Version: 3.8.16
Erlang Version: 23.3.4
Dot Net Client Version: 5.1.2

Since upgrading to 3.8.16 from 3.8.14 we are seeing that a consumer is being shutdown if processing of the received message takes longer than 15 minutes.

The queue is a Durable, Single Access Consumer queue
I am using the 3-management docker image for this test.

Output from my test, the handler should simply wait for 20 minutes then acknowledge the message

Received Msg : 0, 1 (0)
Waiting for 20 minutes 11/05/2021 14:52:27
[Shutdown Handler] Model shutdown 11/05/2021 15:08:26
[Shutdown Handler] AMQP close-reason, initiated by Peer, code=406, text='PRECONDITION_FAILED - consumer ack timed out on channel 1', classId=0, methodId=0
Wait complete

Same test running against RabbitMQ Version: 3.8.14

Received Msg : 0, 1 (0)
Waiting for 20 minutes 11/05/2021 15:13:34
Wait complete
@michaelklishin
Copy link
Member

This is by design: introduced in #2990. See 3.8.15 release notes. The value is configurable.

michaelklishin added a commit to rabbitmq/rabbitmq-website that referenced this issue May 11, 2021
michaelklishin added a commit that referenced this issue May 11, 2021
Apparently 15 minutes is not enough for some. 1 hour seems to be
unreasonably long to our team, though.

References #2990, #3032
michaelklishin added a commit that referenced this issue May 11, 2021
in the logs and consumer channel error message.

References #2990, #3032.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants