You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Assume that the program forgets to acknowledge the message (or processing of the message takes too long).
After a certain timeout (30 minutes by default) the server closes the channel:
If a consumer does not ack its delivery for more than the timeout value (30 minutes by default), its channel will be closed with a PRECONDITION_FAILED channel exception. The error will be [logged](https://www.rabbitmq.com/logging.html) by the node that the consumer was connected to. All outstanding deliveries on that channel, from all consumers, will be [requeued](https://www.rabbitmq.com/confirms.html#automatic-requeueing).
This error will be even propagated to the client but the stream doesn't handle it and will just be idle forever.
I guess that if AMQPChannel#value.isOpen == false, the stream must be interrupted.
Will it be a correct behavior? If yes - I can try to fix it.
The text was updated successfully, but these errors were encountered:
Assume that the program forgets to acknowledge the message (or processing of the message takes too long).
After a certain timeout (30 minutes by default) the server closes the channel:
https://www.rabbitmq.com/consumers.html
This error will be even propagated to the client but the stream doesn't handle it and will just be idle forever.
I guess that if
AMQPChannel#value.isOpen == false
, the stream must be interrupted.Will it be a correct behavior? If yes - I can try to fix it.
The text was updated successfully, but these errors were encountered: