Bug 438218

Summary:	Make temp queues for jms topics identifiable by topic name
Product:	Red Hat Enterprise MRG	Reporter:	Justin Ross <jross>
Component:	qpid-java	Assignee:	Arnaud Simon <asimon>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Kim van der Riet <kim.vdriet>
Severity:	low	Docs Contact:
Priority:	high
Version:	beta	CC:	iboverma
Target Milestone:	---
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2009-08-21 15:43:17 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 Justin Ross 2008-03-19 18:44:28 UTC

The jms client creates temporary queues for messages sent using jms topics. 
These temporary queue names do not contain the jms topic names, so it's not
possible to tell which queues correspond to what topics in the mgmt console.

We ought to embed the topic name in the temporary queue name.  Carl posted a
proposal for this to qpid-list.

Comment 1 Alan Conway 2008-04-29 17:42:47 UTC

The customer wants to be able to use federation with temporary reply-to queues. 

An alternative approach would be to have federation links automatically created
for temporary reply-to queues.

Comment 2 Alan Conway 2008-04-30 13:34:58 UTC

Ignore comment #1 above, the federation issue is a separate bug:
https://bugzilla.redhat.com/show_bug.cgi?id=444742

Comment 3 Arnaud Simon 2008-05-06 15:40:18 UTC

We are now using the following format: 
<binding-key>@<exchange-name>_<uuid>

where
<uuid> is a 36 character UUID string produced (for example) by
java.util.randomUUID().toString()
<binding-key> is a maximum of 207 single-byte characters from the
binding key used.
<exchange-name> is as many characters as possible from the name of the
exchange while still fitting into a 255 character queue-name.