[
https://issues.apache.org/jira/browse/ARTEMIS-1093?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15977050#comment-15977050
]
ASF GitHub Bot commented on ARTEMIS-1093:
-----------------------------------------
Github user gaohoward commented on the issue:
https://github.com/apache/activemq-artemis/pull/1215
There might be a problem with Jenkins machine, the failure relates to
'memory allocation'. Not related to my PR.
@clebertsuconic I ran the whole test suite on my local machine, there are
few test failures but none of them related to my PR. They failed both with and
without my PR. (I'll investigate those failures further when I got time).
> Full qualified queue name support
> ---------------------------------
>
> Key: ARTEMIS-1093
> URL: https://issues.apache.org/jira/browse/ARTEMIS-1093
> Project: ActiveMQ Artemis
> Issue Type: Bug
> Components: Broker
> Affects Versions: 2.0.0
> Reporter: Howard Gao
> Assignee: Howard Gao
> Fix For: 2.next
>
>
> 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
(v6.3.15#6346)
