Bug 508699

Summary: Queue chapter: Document when the exclusive queue is released to next subscriber
Product: Red Hat Enterprise MRG Reporter: Jonathan Robie <jonathan.robie>
Component: Messaging_Programming_ReferenceAssignee: Alison Young <alyoung>
Status: CLOSED CURRENTRELEASE QA Contact: MRG Quality Engineering <mrgqe-bugs>
Severity: medium Docs Contact:
Priority: low    
Version: 1.2CC: alyoung, gsim
Target Milestone: 1.3Keywords: Documentation
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-03-17 01:27:21 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Jonathan Robie 2009-06-29 14:33:25 UTC
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...

Comment 1 Jonathan Robie 2010-03-26 13:50:33 UTC
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?

Comment 2 Jonathan Robie 2010-03-26 22:09:12 UTC
Fixed in checked-in source, will show in next build.

Comment 3 Alison Young 2011-03-17 01:27:21 UTC
Closed as fix already implemented