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

Broker does not communicate with client after "java.lang.IllegalStateException: queue belongs to address<address_name>"

    XMLWordPrintable

Details

    • Bug
    • Resolution: Done
    • Major
    • None
    • AMQ 7.0.1.GA
    • None
    • None
    • Hide

      Connect a receiver to FQQN address::someQueueUnderAnotherAddress.
      --------------------------------------------------------------------------------------------------------

      • Download AMQ Broker zip
      • Unzip it
      • Create instance with command: 
        [...]/artemis create --http-host=0.0.0.0 --force --nio --role=amq --user=admin --allow-anonymous --password=admin --java-options="-Dcom.sun.management.jmxremote=true -Dcom.sun.management.jmxremote.port=1099 -Dcom.sun.management.jmxremote.rmi.port=1099 -Dcom.sun.management.jmxremote.ssl=false -Dcom.sun.management.jmxremote.authenticate=false " --name=amq <some_path>
      • Add multicast prefix to the end of amqp acceptor: 
        ;multicastPrefix=topic://
      • Add two multicast addresses to the addresses section in broker.xml: 
                 <address name="address1">
            <multicast>
               <queue name="address1" />
            </multicast>
         </address>
         <address name="address2">
            <multicast>
               <queue name="address2" />
            </multicast>
         </address>
      • Run broker: 
        <some_path>/bin/artemis run
      • Install packages:
        • qpid-proton-cpp (0.16.0-3)
        • qpid-proton-cpp-devel (0.16.0-3)
        • qpid-proton-cpp-docs (0.16.0-3)
      • Go to path /usr/share/proton-0.16.0/examples/cpp
      • Run: 
        cmake .
      • Run: 
        make simple_recv
      • Run: 
        ./simple_recv "<IP>:5672/topic://address1::address2"
      Show
      Connect a receiver to FQQN address::someQueueUnderAnotherAddress . -------------------------------------------------------------------------------------------------------- Download AMQ Broker zip Unzip it Create instance with command: [...]/artemis create --http-host=0.0.0.0 --force --nio --role=amq --user=admin --allow-anonymous --password=admin --java-options="-Dcom.sun.management.jmxremote=true -Dcom.sun.management.jmxremote.port=1099 -Dcom.sun.management.jmxremote.rmi.port=1099 -Dcom.sun.management.jmxremote.ssl=false -Dcom.sun.management.jmxremote.authenticate=false " --name=amq <some_path> Add multicast prefix to the end of amqp acceptor: ;multicastPrefix=topic:// Add two multicast addresses to the addresses section in broker.xml: <address name="address1"> <multicast> <queue name="address1" /> </multicast> </address> <address name="address2"> <multicast> <queue name="address2" /> </multicast> </address> Run broker: <some_path>/bin/artemis run Install packages: qpid-proton-cpp (0.16.0-3) qpid-proton-cpp-devel (0.16.0-3) qpid-proton-cpp-docs (0.16.0-3) Go to path /usr/share/proton-0.16.0/examples/cpp Run: cmake . Run: make simple_recv Run: ./simple_recv "<IP>:5672/topic://address1::address2"

    Description

      After this exception:

      • AMQ 7.0.1.GA - does not communicate with client and client is stuck (because is expecting attach/close)
      • ActiveMQ Artemis 2.1.0 - sent close with:
        • Condition: amqp:internal-error
        • Description: Unrecoverable error: queue belongs to address<address_name>

      Attachments

        Issue Links

          is cloned by

          Bug - A problem that impairs or prevents the functions of the product. ENTMQBR-795 Implement prefixing in AMQP

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed
          is related to

          Bug - A problem that impairs or prevents the functions of the product. ENTMQBR-855 [OpenWire] Client receives message from Addr2::Q2 when specified Addr1::Q2 by FQQN

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed

          Activity

            People

              mtaylor1@redhat.com Martyn Taylor (Inactive)
              rkubis_kafka_devexp Radim Kubis
              Radim Kubis Radim Kubis
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: