Uploaded image for project: 'JBoss A-MQ'
  1. JBoss A-MQ
  2. ENTMQ-962

Mqtt wildcard inconsistency between fuse 6.1 and 6.2

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Major Major
    • JBoss A-MQ 6.2
    • JBoss A-MQ 6.2
    • mqtt
    • Hide 
      1. unzip fuse 6.1/6.2
2. uncomment default admin user
3. add transport connector: <transportConnector name="mqtt" uri="mqtt://0.0.0.0:1883?maximumConnections=1000&amp;wireFormat.maxFrameSize=104857600"/>
4. run maven clean install in reproducer folder
5. run maven exec:java -Dexec.mainClass=reproducer.MqttWildcard
      Show
      1. unzip fuse 6.1/6.2 2. uncomment default admin user 3. add transport connector: <transportConnector name= "mqtt" uri= "mqtt: //0.0.0.0:1883?maximumConnections=1000&amp;wireFormat.maxFrameSize=104857600" /> 4. run maven clean install in reproducer folder 5. run maven exec:java -Dexec.mainClass=reproducer.MqttWildcard

      There is an inconsistency in mqtt wildcard behavior between fuse 6.1 and 6.2. Publishing to a/b/c/d and subscribing using wildcard +/ +/ + (without spaces) will result in following:

      fuse 6.1 : received msg is null
fuse 6.2 : received msg '', but from topic ActiveMQ/Advisory/MasterBroker

      The question is what is the correct behavior.

        1. reproducer.zip
          5 kB

              dejanbosanac Dejan Bosanac
              avano@redhat.com Andrej Vano
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated:
                Resolved: