Uploaded image for project: 'AMQ Broker'
  1. AMQ Broker
  2. ENTMQBR-6108

An inconsistency was observed in the auto-created queues using a STOMP consumer.

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Not a Bug
    • Icon: Major Major
    • None
    • AMQ 7.9.1.GA
    • stomp-protocol
    • None
    • False
    • False
    • Release Notes, Migration, Compatibility/Configuration, User Experience
    • Hide

      Please use the stock Artemis consumer to listen to a non-existing destination relying on FQQN:

      ./artemis consumer --destination fqqn://bavaria::munchen --message-count 2 --url tcp://localhost:61616 

      The above execution would result in creating an ANYCAST Queue. However, a MULTICAST queue would be created should STOMP protocol be used.

      Show
      Please use the stock Artemis consumer to listen to a non-existing destination relying on FQQN: ./artemis consumer --destination fqqn://bavaria::munchen --message-count 2 --url tcp://localhost:61616  The above execution would result in creating an ANYCAST Queue. However, a MULTICAST queue would be created should STOMP protocol be used.

      An inconsistency was observed in the auto-created queues using a STOMP consumer. The STOMP consumer creates a MULTICAST queue. The same syntax would result in an ANYCAST queue should any other protocol be used.

      However, AMQ 6 works as expected offering consistency irrespective of the protocol being used to create.

        1. broker.xml
          12 kB

              rhn-support-jbertram Justin Bertram
              rhn-support-tywickra Tyronne Wickramarathne
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: