Red Hat Bugzilla – Bug 508699
Queue chapter: Document when the exclusive queue is released to next subscriber
Last modified: 2013-08-05 20:53:43 EDT
For exclusive, we need to be more explicit on when the exclsuive queue will be released to the next subscriber. i.e. based on session closing, and maybe also say that the time can be reduced by configuring heartbeats...
The current text says this:
> Exclusive queues
> Exclusive queues can only be used in one session at a time. When a queue is
> declared with the exclusive property set, that queue is not available for use
> in any other session until the session that declared the queue has been closed.
> If the server receives a declare, bind, delete or subscribe request for a
> queue that has been declared as exclusive, an exception will be raised and the
> requesting session will be ended.
I think that clearly states that the queue is not available until the session that declared the queue has been closed.
I will mention that using heartbeats allows this to be detected more quickly. Is there anything else that needs to be added?
Fixed in checked-in source, will show in next build.
Closed as fix already implemented