<p>Thanks Steve, that's pretty much what Simon had already clarified, and I agreed that changing this behavior is not practical.</p>
<div class="gmail_quote">On Feb 21, 2012 2:24 PM, "Steve Powell" <<a href="mailto:steve@rabbitmq.com">steve@rabbitmq.com</a>> wrote:<br type="attribution"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Simone,<br>
<br>
Replies in-line below..<br>
<br>
I don't think this is likely to change in the near future, since it<br>
would be disruptive to most clients that use this.<br>
<br>
Steve Powell �(a happy bunny)<br>
----------some more definitions from the SPD----------<br>
vermin (v.) Treating the dachshund for roundworm.<br>
chinchilla (n.) Cooling device for the lower jaw.<br>
socialcast (n.) Someone to whom everyone is speaking but nobody likes.<br>
<br>
On 16 Feb 2012, at 17:10, Busoli, Simone wrote:<br>
<br>
> Without relying on the management plugin I think the only way to do that is to<br>
> declare the queue as passive. At least with the .NET client and apparently the<br>
> Java client too, when the queue does not exist, besides throwing an exception,<br>
> the channel is closed as well. From the spec:<br>
><br>
> If set, the server will reply with Declare-Ok if the queue already exists with<br>
> the same name, and raise an error if not. The client can use this to check<br>
> whether a queue exists without modifying the server state.<br>
<br>
The spec goes on to say:<br>
<br>
�The client MAY ask the server to assert that a queue exists without creating<br>
�the queue if not. If the queue does not exist, the server treats this as a<br>
�failure. Error code: not-found<br>
<br>
> There is no mention of channel closure, while the last sentence implies that<br>
> using the passive bit is indeed a way for a client to check queue existence, so<br>
> closing the channel when it doesn�t is a bit unexpected. That said, it�s not a<br>
> big deal to recreate the channel in such cases, but I�d appreciate your opinion.<br>
> Any chance this behavior can be changed in the client libraries?<br>
<br>
This is the mention of channel-closure -- an 'error' raised on the channel will<br>
close it.<br>
<br>
_______________________________________________<br>
rabbitmq-discuss mailing list<br>
<a href="mailto:rabbitmq-discuss@lists.rabbitmq.com">rabbitmq-discuss@lists.rabbitmq.com</a><br>
<a href="https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss" target="_blank">https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss</a><br>
</blockquote></div>