[rabbitmq-discuss] durability = true & auto delete = true
sp345s at att.com
Tue Jul 1 15:41:26 BST 2014
Thanks Michael ..
Can you pl. help with the below ..
Also we are setting the TTL for the messages.. but our requirement is every client has a separate TTL for the messages … We want to check is there any option we can set when client creates the queues with durability = true & auto delete = true
From: Michael Klishin [mailto:mklishin at gopivotal.com]
Sent: Tuesday, July 01, 2014 9:55 AM
To: PATAR, SAGAR; Legacy list about RabbitMQ
Subject: Re: [rabbitmq-discuss] durability = true & auto delete = true
On 1 July 2014 at 17:48:53, PATAR, SAGAR (sp345s at att.com) wrote:
> durability = true & auto delete = true ??
> What will happen to the messages in the queue when a connection
> is lost??
If the queue is exclusive, the durability attribute has no effect
because the queue will be deleted as soon as client disconnects
(or its connection is lost).
auto-deleted queues are deleted when the last consumer is cancelled
(or its channel is closed, or its connection is lost).
If there never was a consumer (e.g. you only use basic.get), it won't
Obviously, when a queue is deleted, all messages in it are also deleted.
> Will the Queues be mirrored across the cluster .. what parameter
> needs to be set to make them mirrored ??
> Also wanted to check if rabbit MQ generates a message ID which
> is unique and sequential ?? and can be used in java code to identify
> the point of failure?
RabbitMQ does not generate message ids that are exposed to clients. Do not rely
on delivery tags for anything.
Staff Software Engineer, Pivotal/RabbitMQ
More information about the rabbitmq-discuss