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/08 08:39:20 UTC
[jira] [Assigned] (ARTEMIS-1205) AMQP Shared Durable Subscriber
incorrect behaviour.
[ https://issues.apache.org/jira/browse/ARTEMIS-1205?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Michael Andre Pearce reassigned ARTEMIS-1205:
---------------------------------------------
Assignee: Michael Andre Pearce
Affects Version/s: 2.0.0
2.1.0
Fix Version/s: 2.2.0
> AMQP Shared Durable Subscriber incorrect behaviour.
> ---------------------------------------------------
>
> Key: ARTEMIS-1205
> URL: https://issues.apache.org/jira/browse/ARTEMIS-1205
> Project: ActiveMQ Artemis
> Issue Type: Bug
> Affects Versions: 2.0.0, 2.1.0
> Reporter: Michael Andre Pearce
> Assignee: Michael Andre Pearce
> Priority: Blocker
> Fix For: 2.2.0
>
> Attachments: AMQPMissbehaviour.xlsx, JMSDurableConsumerTest2.java, JMSSharedDurableConsumerTest.java
>
>
> 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
(v6.3.15#6346)