activemq-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <>
Subject [jira] [Commented] (ARTEMIS-1093) Full qualified queue name support
Date Wed, 05 Apr 2017 13:49:41 GMT


ASF GitHub Bot commented on ARTEMIS-1093:

Github user clebertsuconic commented on the issue:
    @gaohoward  for something like this you should have talked to us through a DISCUSS thread,
or talked about some design first...
    There's WildcardConfiguration already...
    this is a big change, and I don't like it much.. it adds a complext piece of a referenceCounting
on this Key, plus some concatenations to lookup for Addresses... 
    I'm really concerned about letting this change go in...
    Can't we have a simpler change.. perhaps use the WildcardAddressManager in any way? what
it is needed that is not covered by that already?

> Full qualified queue name support
> ---------------------------------
>                 Key: ARTEMIS-1093
>                 URL:
>             Project: ActiveMQ Artemis
>          Issue Type: Bug
>          Components: Broker
>    Affects Versions: 2.0.0
>            Reporter: Howard Gao
>            Assignee: Howard Gao
>             Fix For:
> Broker should support full qualified queue names (FQQN) as well as bare queue names.
This means when clients access to a queue they have two equivalent ways to do so. One way
is by queue names and the other is by FQQN (i.e. address::qname) names. When accessing a queue
by its bare name, it is required that the name should be unique across all addresses.
> Otherwise a warning is given and client should use FQQN instead.

This message was sent by Atlassian JIRA

View raw message