From RabbitMQ documents I see that if a queue created with durable: true and a message sent to this queue with persistent: true the message will be resent in case of RabbitMQ service crash before an ack sent for this message (in most cases, and if noAck: false).
What will happen if a message is sent with persistent: true but a queue was created with durable: false?
And is there any scenario that such configuration (persistent: true & durable: false) can make sense?
And is there any scenario that such configuration (persistent: true & durable: false) can make sense?
Not really. In fact, support for non-exclusive, non-durable queues will be removed in RabbitMQ 4.0.
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With