Uploaded image for project: 'AMQ Documentation'
  1. AMQ Documentation
  2. AMQDOC-2854

Dev - Addressing - Clarify current behavior of auto-creating a queue for a non-JMS client

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Critical Critical
    • None
    • 7.0
    • Broker DOC

      The discussion on ENTMQBR-906 was quite lengthy. Trying to capture the doc task accurately here; the updated content requires careful SME review.

      Section requiring revision:
      https://access.redhat.com/documentation/en-us/red_hat_jboss_amq/7.0/html/using_amq_broker/addresses#auto_create_queues_addresses

      Clarification from Andy T to use as fodder:
      "so we need to add the following to that section of the doc, something like:
      When addresses and queues are auto created a decision is made as to what Routing Type they will have, either Anycast or Multicast. Usually the routing type can be inferred from the client, for instance if the client is JMS and sending or receiving from a JMS topic then an multicast address is created or if the client is a sending or receiving to a JMS queue then an anycast address with an anycast queue is created. Sometimes however this information cannot be deduced for instance when an amqp sender sends a message so in this case the address setting <default-address-routing-type> is used to make this decision. Warning: By default this is multicast so if you send a message to an address or queue that doesn't exist then this message will only be forwarded to consumers if they exist, if none exist then this message will just disappear and be lost."

            jcliffor@redhat.com John Clifford
            sjay@redhat.com Susan Jay
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated: