activemq-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Michael Andre Pearce (JIRA)" <>
Subject [jira] [Commented] (ARTEMIS-1205) AMQP Shared Durable Subscriber incorrect behaviour.
Date Mon, 05 Jun 2017 14:38:04 GMT


Michael Andre Pearce commented on ARTEMIS-1205:


"Its probably worth noting that changing the queue name in the manner from the PR looks like
it moves the no-ClientID shared durable subscription backing queue names into the same namespace
as regular queues, which might lead to unexpected behaviour at times. Seperately, the change
in name doesnt itself pose any more of an issue (in terms of orphaned messages on old queues)
for people upgrading than the existing behaviour already did that would give them a different
queue name with each connection."

This moves it to the same name as artemis core does, so from a queue name space it will be
the same, the bonus being it will mean actually can share a subscription safefly between a
AMQP and Core client, this is included in the added integration tests. The fact shared subscriber
simply was not functional before when using AMQP there shouldn't be upgrade issue as feature
simply wasn't working. 

> AMQP Shared Durable Subscriber incorrect behaviour.
> ---------------------------------------------------
>                 Key: ARTEMIS-1205
>                 URL:
>             Project: ActiveMQ Artemis
>          Issue Type: Bug
>            Reporter: Michael Andre Pearce
>            Priority: Blocker
>         Attachments: AMQPMissbehaviour.xlsx,,
> Summary observations :
> •	There’s different behaviour between AMQP and the Artemis clients
> •	There's UUID subscription name in the subscription topic when you’re using the
AMQP client, you don’t set the client ID and you’ve selected a durable & shared subscription.
It should just be the subscription name, like with the Artemis client.
> •	The AMQP client seems to have a problem if you try to create a new durable, non-shared
subscription on the same topic with the same client ID and a different subscription name.
> The artemis client doesn’t have a problem with this.

This message was sent by Atlassian JIRA

View raw message