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

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

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Not a Bug
    • Icon: Major Major
    • None
    • AMQ 7.1.0.GA
    • broker-core, stomp-protocol
    • None
    • Workaround Exists
    • Hide

      Don't use auto created destinations.

      Show
      Don't use auto created destinations.

      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\n" +
      "destination:queue/foo\n" +
      "\n" +
      text +
      END_OF_FRAME;

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

      "SEND\n" +
      "destination:queue/foo\n" +
      "destination-type:ANYCAST\n" +
      "\n" +
      text +
      END_OF_FRAME;

      but that is non standart since there is no destination-type header defined in STOMP protocol.

              rh-ee-ataylor Andy Taylor
              rhn-support-toross Tom Ross
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

                Created:
                Updated:
                Resolved: