forked from rabbitmq/rabbitmq-server
-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Skip access check on absent will queue
Resolves rabbitmq#11021 Prior to this commit, an MQTT client that connects to RabbitMQ needed configure access to its will queue even if the will queue has never existed. This breaks client apps connecting with either v3 or v4 or with v5 without making use of the Will-Delay-Interval. Specifically, in 3.13.0 and 3.13.1 an MQTT client that connects to RabbitMQ needs unnecessarily configure access to queue `mqtt-will-<MQTT client ID>`. This commit only check for configure access, if the queue actually gets deleted, i.e. if it existed.
- Loading branch information
Showing
2 changed files
with
36 additions
and
26 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters