You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@activemq.apache.org by "Timothy Bish (JIRA)" <ji...@apache.org> on 2014/08/07 02:10:12 UTC

[jira] [Comment Edited] (AMQ-5290) MQTT clients using durable subscriptions on networked brokers received duplicates

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

Timothy Bish edited comment on AMQ-5290 at 8/7/14 12:08 AM:
------------------------------------------------------------

Yes, it gets a bit funky when you starting having the more complicated destination features in the mix.  For instance you can't create a durable subscription to a Virtual Topic like "VirtualTopic.FOO" because things get mixed up when you try to find you connection's previous subscriptions on reconnect due to all the name munging.  


was (Author: tabish121):
Yes, it gets a bit funky when you starting having the more complicated destination features.  For instance you can't crate a durable subscription to a Virtual Topic like "VirtualTopic.FOO" because things get mixed up when you try to find you connection's previous subscriptions on reconnect due to all the name munging.  

> MQTT clients using durable subscriptions on networked brokers received duplicates
> ---------------------------------------------------------------------------------
>
>                 Key: AMQ-5290
>                 URL: https://issues.apache.org/jira/browse/AMQ-5290
>             Project: ActiveMQ
>          Issue Type: Improvement
>          Components: MQTT
>    Affects Versions: 5.10.0
>            Reporter: Timothy Bish
>             Fix For: 5.11.0
>
>
> MQTT clients that create durable subscriptions and that operate in a network of Brokers can receive duplicate messages when they start failing back and forth between brokers in the network.
> We should investigate using Virtual Destinations under the covers instead of durable topics subscriptions as this is a known problem with the durable topic case.  With Virtual Destinations the client would be subscribed to a Queue that would receive all messages sent to the target Topic.  



--
This message was sent by Atlassian JIRA
(v6.2#6252)