[ 
https://issues.apache.org/jira/browse/ARTEMIS-1205?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16037097#comment-16037097
 ] 

Michael Andre Pearce edited comment on ARTEMIS-1205 at 6/5/17 3:42 PM:
-----------------------------------------------------------------------

[~gemmellr]
Glad we're agreed :)

Re the one final comment.
"I realise, I wasn't really commenting on that aspect...more that it looks (I 
might be mistaken, I haven't tried it) to also be the same namespace as regular 
(non 'topic subscription backing') queues which could give unexpected 
behaviour, e.g during unsubscribe is it possible Bad Things (TM) might happen 
to a queue named in line with an otherwise unrelated topic subscription?"

All the same risks, as per the core client, this is the address and queue model 
implemented in core artemis, so if this is true, then there is a lot larger 
issues with the core underlying design (but I'm sure this was thought about 
when being implemented, and we shouldn't worry).

[~tabish121] agreed, i think that issue is separate, we can track separately. 
raised https://issues.apache.org/jira/browse/ARTEMIS-1206



was (Author: michael.andre.pearce):
[~gemmellr]
Glad we're agreed :)

Re the one final comment.
"I realise, I wasn't really commenting on that aspect...more that it looks (I 
might be mistaken, I haven't tried it) to also be the same namespace as regular 
(non 'topic subscription backing') queues which could give unexpected 
behaviour, e.g during unsubscribe is it possible Bad Things (TM) might happen 
to a queue named in line with an otherwise unrelated topic subscription?"

All the same risks, as per the core client, this is the address and queue model 
implemented in core artemis, so if this is true, then there is a lot larger 
issues with the core underlying design (but I'm sure this was thought about 
when being implemented, and we shouldn't worry).

[~tabish121] agreed, i think that issue is separate, we can track separately.


> AMQP Shared Durable Subscriber incorrect behaviour.
> ---------------------------------------------------
>
>                 Key: ARTEMIS-1205
>                 URL: https://issues.apache.org/jira/browse/ARTEMIS-1205
>             Project: ActiveMQ Artemis
>          Issue Type: Bug
>            Reporter: Michael Andre Pearce
>            Priority: Blocker
>         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)

Reply via email to