[rabbitmq-discuss] RabbitMQ queue durability question

[Jan Jacobs]

Hi,

I have the following environment:
Server: (Language: Erlang, Version: 2.7.1)
Broker: (Version: 3.1.5)
Client: (Language: Grails/Groovy, Version: 2.8.4)

I am using RPC functionality over the broker.
A queue is created by the server or the client has the following 
configuration:
|auto delete|, |durable| and |exclusive| attributes are set to |false|

The problem:
If the client and the server is not active and the broker restarts the 
queue does not survive the restart and it behaves as required.
If the client and the server is active and the broker restarts then the 
broker change the queue durability to|durable|: true and it survives the 
restart.

This causes chaos with the server behaviour.
The server tries to recover the connection and recreate the queue with 
configuration of |auto delete|, |durable| and |exclusive| attributes are 
set to |false. |In turn the creation of the queue to fails because of 
the changed durability.

Why does the broker change the durability of the queue?
Is that the correct behaviour?

Any help or advice shall be highly appreciated.

Thanks
-- 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rabbitmq.com/pipermail/rabbitmq-discuss/attachments/20130903/38786a47/attachment.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: JanEmailSignature.gif
Type: image/gif
Size: 9261 bytes
Desc: not available
URL: <http://lists.rabbitmq.com/pipermail/rabbitmq-discuss/attachments/20130903/38786a47/attachment.gif>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: janj.vcf
Type: text/x-vcard
Size: 167 bytes
Desc: not available
URL: <http://lists.rabbitmq.com/pipermail/rabbitmq-discuss/attachments/20130903/38786a47/attachment.vcf>