Replies: 1 comment 3 replies
-
A blocked publishing connection in and of itself won't be closed. It can be closed after a period of time due to missed heartbeats but in modern RabbitMQ series, the server will pause heartbeat tracking for such connections. The client, however, won't IIRC. In any case, the shutdown signals is not what you are looking for. There is a separate notification that this client has supported since day one of that protocol extension, for over a decade. |
Beta Was this translation helpful? Give feedback.
3 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Hello there,
when the broker has insufficient disk space and is blocking publishers, a publisher confirm may reach the timeout and the channel closes. However, a consumer on the same channel never gets the ShutdownSignal in this case because this line is never executed. Besides Publisher Confirm, this also applies if you call
channel.abort()
when the broker is blocking. The ShutdownSignal is not broadcasted to consumers. Is that behaviour intended?I'm asking because we are using the
vertx-rabbitmq-client
which uses only one channel per connection and restores a consumer when a ShutdownSignal is broadcasted which is not working when the case described above happens.Thank you!
Beta Was this translation helpful? Give feedback.
All reactions