[ https://issues.apache.org/jira/browse/ARTEMIS-1205?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16043286#comment-16043286 ]
ASF GitHub Bot commented on ARTEMIS-1205: ----------------------------------------- Github user clebertsuconic commented on the issue: https://github.com/apache/activemq-artemis/pull/1316 ``` For us the alignment is fairly critical, as we will have shared core and amqp env ``` Are you sure you need this in production? or that's a testcase only. anyways.. I"m out for 2 weeks starting tomorrow... I'm trying to get a shock treatment to get away from the iphone as much as I can. :) > 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)