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

Timothy Bish edited comment on AMQ-5290 at 8/12/14 7:00 PM:
------------------------------------------------------------

Added a proof of concept that utilizes virtual topics for subscriptions if the 
virtual topic subscription strategy is enabled, otherwise uses the standard 
durable topics subscriptions as always. 

To enable the transport connector needs to add the option:

{noformat}
?transport.subscriptionStrategy="mqtt-virtual-topic-subscriptions"
{noformat}


was (Author: tabish121):
Added a proof of concept that utilizes virtual topics for subscriptions if the 
virtual topic subscription strategy is enabled, otherwise uses the standard 
durable topics subscriptions as always. 

To enable the transport connector needs to add the option:

{noformat}
?transport.subscriptionStrategyName="mqtt-virtual-topic-subscriptions"
{noformat}

> 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)

Reply via email to