You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@activemq.apache.org by "Michael Andre Pearce (JIRA)" <ji...@apache.org> on 2017/06/07 01:00:40 UTC
[jira] [Updated] (ARTEMIS-1210) Queue name should create Queue with
Address in its name by default
[ https://issues.apache.org/jira/browse/ARTEMIS-1210?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Michael Andre Pearce updated ARTEMIS-1210:
------------------------------------------
Summary: Queue name should create Queue with Address in its name by default (was: Queue name should create Queue with address in its name by default)
> 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.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)