[
https://issues.apache.org/jira/browse/ARTEMIS-1205?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16055417#comment-16055417
]
ASF subversion and git services commented on ARTEMIS-1205:
----------------------------------------------------------
Commit 1bfa1ad4fe9e6e8fae9346522e58d3e59f7fc2fa in activemq-artemis's branch
refs/heads/master from [~michael.andre.pearce]
[ https://git-wip-us.apache.org/repos/asf?p=activemq-artemis.git;h=1bfa1ad ]
ARTEMIS-1205: AMQP Shared Durable Subscriber - Document Update
Update documents for new configuration toggle for
'amqp-use-core-subscription-naming '
> 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.4.14#64029)
