Mailing-List: contact issues-help@activemq.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@activemq.apache.org
Date: Wed, 7 Jun 2017 07:11:18 +0000 (UTC)
From: "Michael Andre Pearce (JIRA)" <jira@apache.org>
To: issues@activemq.apache.org
Message-ID: <JIRA.13077848.1496795874000.15399.1496819478200@Atlassian.JIRA>
In-Reply-To: <JIRA.13077848.1496795874000@Atlassian.JIRA>
References: <JIRA.13077848.1496795874000@Atlassian.JIRA> <JIRA.13077848.1496795874582@jira-lw-us.apache.org>
Subject: [jira] [Resolved] (ARTEMIS-1210) Queue name should create Queue
 with Address in its name by default
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Wed, 07 Jun 2017 07:11:23 -0000


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

Michael Andre Pearce resolved ARTEMIS-1210.
-------------------------------------------
    Resolution: Not A Problem

> Queue name should create Queue with Address in its name by default
> ------------------------------------------------------------------
>
>                 Key: ARTEMIS-1210
>                 URL: https://issues.apache.org/jira/browse/ARTEMIS-1210
>             Project: ActiveMQ Artemis
>          Issue Type: Bug
>            Reporter: Michael Andre Pearce
>
> When making a consumer for a topic (multicast) address, a queue is created named with for shared subscriber just the subscription name and if present client id only or in case of durable consumer it is the clientid + name only.
> This causes issue where client can validly use the same name's but for different address's.
> e.g.
> 2017-06-07 01:33:21.144  WARN 70432 --- [nerContainer-28] o.s.j.l.DefaultMessageListenerContainer  : Setup of JMS message listener invoker failed for destination 'com.ig.trading.v0.order.history' - trying to recover. Cause: AMQ119082: Queue opstest already exists on another subscription
> To avoid this clash including the address in the queue name (as like for any cast queues) would solve this issue.
> Also it seems https://activemq.apache.org/artemis/docs/2.1.0/address-model.html alludes that actually this is the behaviour to include the address name in the consumer queue name.
> A clunky work around is obviously for the clients to ensure the name is globally unique by manually postfix'ing or prefix'ing the topic/address name. Though if this is the way forward the documents for address-model need to be updated with this detail, and avoid alluding to the pattern that the address is added by the system. Likewise frameworks like Spring would make a work around approach very fragile.


--
This message was sent by Atlassian JIRA
(v6.3.15#6346)