activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Netlancer (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AMQ-5365) MQTT topic name in received message is wrong in network of brokers scenario
Date Fri, 17 Oct 2014 17:32:34 GMT

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

Netlancer commented on AMQ-5365:
--------------------------------

Works with the following modified onSend method in MQTTVirtualTopicSubscriptionStrategy 

    @Override
    public String onSend(ActiveMQDestination destination) {
        String amqTopicName = destination.getPhysicalName();
        int idx = amqTopicName.indexOf(VIRTUALTOPIC_PREFIX);
        if (idx > 0) {
            amqTopicName = amqTopicName.substring(idx + VIRTUALTOPIC_PREFIX.length());
            LOG.debug("onSend TopicName = {} ",amqTopicName);
        }
        return amqTopicName;
    }


> MQTT topic name in received message is wrong in network of brokers scenario
> ---------------------------------------------------------------------------
>
>                 Key: AMQ-5365
>                 URL: https://issues.apache.org/jira/browse/AMQ-5365
>             Project: ActiveMQ
>          Issue Type: Bug
>          Components: MQTT
>    Affects Versions: 5.11.0
>            Reporter: AR
>              Labels: mqtt, networkofbrokers
>
> Setup:
> Broker1 and Broker2 are networked using a duplex connection.
> <Broker1> -------------- <Broker2>
> Transport connector of Broker1:
> -----------------------------------------
> <transportConnector name="mqtt"uri="mqtt://0.0.0.0:1883?maximumConnections=1000&amp;wireFormat.maxFrameSize=104857600&amp;transport.subscriptionStrategy=mqtt-virtual-topic-subscriptions”/>
> Transport connector of Broker2:
> -----------------------------------------
> <transportConnector name="mqtt"uri="mqtt://0.0.0.0:2883?maximumConnections=1000&amp;wireFormat.maxFrameSize=104857600&amp;transport.subscriptionStrategy=mqtt-virtual-topic-subscriptions”/>
> Problem:
> In a network of brokers scenario with MQTT clients, sometimes the topic that is reported
(to the clients) when the message is received has extra information prefixed to what the consumer
subscribed to. For example, if the consumer received a message on topic dup/msg/test, it is
received as:
> Consumer/duptestsub:AT_LEAST_ONCE/VirtualTopic/dup/msg/tes



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message