Skip to content
This repository has been archived by the owner on May 13, 2022. It is now read-only.

Durability conflicts when publishing messages #11

Closed
misl opened this issue Nov 15, 2019 · 1 comment
Closed

Durability conflicts when publishing messages #11

misl opened this issue Nov 15, 2019 · 1 comment
Labels
question A question of RCA request

Comments

@misl
Copy link

misl commented Nov 15, 2019

I am using SmallRye Reactive messaging AMQP connector to connect with RabbitMQ. When not using "durable" things work just fine. Listening to "durable" queue also works fine. However when publishing messages to "durable" queues things go wrong. An I end up with errors like this:

{'v1_0.error',{symbol,<<"amqp:precondition-failed">>},{utf8,<<"PRECONDITION_FAILED - inequivalent arg 'durable' for queue 'prices' in vhost '/': received 'true' but current is 'false'">>},undefined}

This issue has already been reported to Smallrye messaging by someone else in ticket #174. However as an outsider to me it is not very clear where this issue should be fixed, especially when reading this comment. By creating this issue on RabbitMQ side of the fence I just want to make sure both communities are aware of it, in the hope to get some guidance/help in resolving this issue.

Some contextual information. If I am correct SmallRye Messaging AMQP connector is build on top of Vert.X AMQP which uses Apache Qpid Proton-J.

@michaelklishin michaelklishin transferred this issue from rabbitmq/rabbitmq-amqp1.0 Nov 15, 2019
@michaelklishin
Copy link
Member

Queue properties in RabbitMQ are assumed to be immutable except for (some) optional arguments that are controlled via policies.

This is not true for every protocol we support, or at least the specifics of durability and mismatching property handling are different, so in 3.9 this limitation won't apply to the protocols where it does not make much sense. It's going to be a major internal refactoring already planned for 3.9 and not specific to AMQP 1.0.

You have to delete the queue and redeclare it with a different set of arguments, or use a set of properties that match those already present.

@michaelklishin michaelklishin added the question A question of RCA request label Nov 15, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
question A question of RCA request
Projects
None yet
Development

No branches or pull requests

2 participants