Details
-
Bug
-
Status: Resolved
-
Major
-
Resolution: Fixed
-
5.11.0
Description
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&wireFormat.maxFrameSize=104857600&transport.subscriptionStrategy=mqtt-virtual-topic-subscriptions”/>
Transport connector of Broker2:
-----------------------------------------
<transportConnector name="mqtt"uri="mqtt://0.0.0.0:2883?maximumConnections=1000&wireFormat.maxFrameSize=104857600&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