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

declaring queue exclusive disables durable #1476

Open
JanEggers opened this issue Jan 18, 2024 · 3 comments
Open

declaring queue exclusive disables durable #1476

JanEggers opened this issue Jan 18, 2024 · 3 comments
Assignees
Labels
enhancement next-gen-todo If a rewrite happens, address this issue.

Comments

@JanEggers
Copy link
Contributor

Describe the bug

using RabbitMq.Client 6.8.1

var factory = new ConnectionFactory
{
    UserName = "rabbit",
    Password = "rabbit",
    HostName = "localhost",
    VirtualHost = "/",
    Port = 5672,
    AutomaticRecoveryEnabled = true
};


using (var client = factory.CreateConnection())
{
    using var model = client.CreateModel();

    model.QueueDeclare("queue", true, true, false, new Dictionary<string, object>());
}

this code generates a non durable queue

image

when i manually create a durable queue in the management of the broker the queue is created correctly so I assume its a client side issue.

Reproduction steps

x

Expected behavior

the queue is durable

Additional context

No response

@JanEggers
Copy link
Contributor Author

now i found the issue exlusive seems to overrule durable. I think the client should throw in case both options are set.

@JanEggers JanEggers reopened this Jan 18, 2024
@JanEggers JanEggers changed the title unable to declare queue durable declaring queue exclusive disables durable Jan 18, 2024
@lukebakken lukebakken added this to the 7.0.0 milestone Jan 18, 2024
@lukebakken lukebakken self-assigned this Jan 18, 2024
@lukebakken
Copy link
Contributor

now i found the issue exlusive seems to overrule durable. I think the client should throw in case both options are set

We'll take it into consideration for version 7 or 8 of this client.

@lukebakken lukebakken removed this from the 7.0.0 milestone May 12, 2024
@lukebakken lukebakken added the next-gen-todo If a rewrite happens, address this issue. label May 12, 2024
@lukebakken
Copy link
Contributor

FWIW, the Java client does not validate the combination of exclusive & durable.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement next-gen-todo If a rewrite happens, address this issue.
Projects
None yet
Development

No branches or pull requests

2 participants