Uploaded image for project: 'ActiveMQ Artemis'
  1. ActiveMQ Artemis
  2. ARTEMIS-1905

When using JMS API over STOMP protocol only multicast destinations are created

    XMLWordPrintableJSON

Details

    • Bug
    • Status: Resolved
    • Major
    • Resolution: Not A Problem
    • 2.6.0
    • None
    • Broker, STOMP
    • None

    Description

      When calling JMS API createQueue() only multicast destinations are created in the broker back end. The call to createQueue() should result in a anycast destination to be created.

      Also when sending a frame like would result in multicast destination.

      SEND
      destination:queue/foo
      
      text
      

      It's possible to add destination-type header to the frame

      SEND
      destination:queue/foo
      destination-type:ANYCAST
      
      text
      

      However, that is non-standard since there is no destination-type header defined in STOMP protocol.

      Attachments

        Activity

          People

            jbertram Justin Bertram
            raggz Tom Ross
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: