[Questions] Does the broker wait for the client confirmation before closing the connection?

[oskar-wicht]

Community Support Policy

• I have read RabbitMQ's Community Support Policy
• I run RabbitMQ 4.x, the only series currently covered by community support
• I promise to provide all relevant information (versions, logs from all nodes, rabbitmq-diagnostics output, detailed reproduction steps)

RabbitMQ version used

4.2.3

Erlang version used

28.3.x

Operating system (distribution) used

debian-12-r1

How is RabbitMQ deployed?

Community Docker image

rabbitmq-diagnostics status output

See https://www.rabbitmq.com/docs/cli to learn how to use rabbitmq-diagnostics

Details

# PASTE OUTPUT HERE, BETWEEN BACKTICKS

Logs from node 1 (with sensitive values edited out)

See https://www.rabbitmq.com/docs/logging to learn how to collect logs

Details

# PASTE LOG HERE, BETWEEN BACKTICKS

Logs from node 2 (if applicable, with sensitive values edited out)

See https://www.rabbitmq.com/docs/logging to learn how to collect logs

Details

# PASTE LOG HERE, BETWEEN BACKTICKS

Logs from node 3 (if applicable, with sensitive values edited out)

See https://www.rabbitmq.com/docs/logging to learn how to collect logs

Details

# PASTE LOG HERE, BETWEEN BACKTICKS

rabbitmq.conf

See https://www.rabbitmq.com/docs/configure#config-location to learn how to find rabbitmq.conf file location

Details

# PASTE rabbitmq.conf HERE, BETWEEN BACKTICKS

Steps to deploy RabbitMQ cluster

Not applicable

Steps to reproduce the behavior in question

Not applicable

advanced.config

See https://www.rabbitmq.com/docs/configure#config-location to learn how to find advanced.config file location

Details

# PASTE advanced.config HERE, BETWEEN BACKTICKS

Application code

Details

# PASTE CODE HERE, BETWEEN BACKTICKS

Kubernetes deployment file

Details

# Relevant parts of K8S deployment that demonstrate how RabbitMQ is deployed
# PASTE YAML HERE, BETWEEN BACKTICKS

What problem are you trying to solve?

When the broker wants to close the AMQP connection it sends the connection.close command to the client as far as I understand. Does it actually wait for the client to confirm with connection.close-ok before closing the socket?

[michaelklishin]

Client connections are closed in only a few scenarios:

1. The node is shutting down (or a plugin is)
2. A user was deleted
3. A connection was intentionally closed by a human operator using CLI tools or the HTTP API
4. A client operation has resulted in an unrecoverable protocol error (e.g. you try to open a channel with an ID that's already allocated for another channel)

I don't think it makes any practical difference in either of those cases but the answer is "yes, it does, with a timeout".

With multiple timeouts, in fact, the heartbeat mechanism also acts as a timeout during a portion of the shutdown, plus a hard cap of 30 seconds (the ?CLOSING_TIMEOUT value).

Multiple connections are terminated in parallel. So the longest wait in the worst case scenario will be about 30 seconds for all connections of a user/on a node. During a shutdown, even less so because the server will stop its listeners at some point.