You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "Aidan Skinner (JIRA)" <qp...@incubator.apache.org> on 2008/07/24 11:13:32 UTC

[jira] Updated: (QPID-1030) Making JMS easier for users

     [ https://issues.apache.org/jira/browse/QPID-1030?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Aidan Skinner updated QPID-1030:
--------------------------------

    Assignee: Arnaud Simon

> Making JMS easier for users
> ---------------------------
>
>                 Key: QPID-1030
>                 URL: https://issues.apache.org/jira/browse/QPID-1030
>             Project: Qpid
>          Issue Type: Improvement
>          Components: Java Client
>    Affects Versions: M3
>            Reporter: Arnaud Simon
>            Assignee: Arnaud Simon
>             Fix For: M3
>
>
> This Jira is related to the mailing list thread: "Making JMS easier for users" (Note: I haven't found one related to this thread, please just mark that issue as duplicated if one already exists) 
> Issue, when we setup JMS topics is that it creates a tmp queue for each connection with an ugly name. This makes it hard for admins to map the temp queues to the topics.
> It has been decided that the following scheme should be used: 
> <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.
> this would give queue names like
> stocks.nyse.*@amq.direct_47c1b90d-2eb6-4245-a0e2-e07c2547bf7d

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.