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

[A-MQ7 Broker, A-MQ 6 OpenWire Client, message-load-balancing=ON_DEMAND ] Periodically, messages continually traversing cluster when no consumers are connected

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Major Major
    • A-MQ 7.0.0.ER17
    • A-MQ 7.0.0.ER12
    • None
    • Hide

      1)setup broker cluster with config attached - 2 brokers statically configured, using ON_DEMAND and redistribution-delay = 0 (attaching config files for brokers)

      2)produce 5000 messages to broker1 using standard artemis client

      ./artemis  producer --url tcp://localhost:61616 --message-count 5000

      3) Consume 100 messages using A-MQ 6 standard client attaching to broker2

      java -jar /opt/a-mq-6/activemq-all.jar  consumer --brokerUrl tcp://localhost:61716 --user admin --password admin --destination TEST --messageCount 100

      4) Consume 100 messages using A-MQ 6 standard client attaching to broker1

      java -jar activemq-all-5.11.0.redhat-630187.jar  consumer --brokerUrl tcp://localhost:61616 --user admin --password admin --destination TEST --messageCount 100

      Steps 3 and 4 force the messages to migrate across the network as expected. However after multiple interations of step 3 and step 4 in the JMX console the messages appear to be traversing the network in a quick continuous loop even when no consumer is attached to the brokers.

      NOTE: activemq-all-5.11.0.redhat-630187.jar is found in the jboss-a-mq-6.3.0.redhat-187/extras/apache-activemq-5.11.0.redhat-630187-bin.zip

      Show
      1)setup broker cluster with config attached - 2 brokers statically configured, using ON_DEMAND and redistribution-delay = 0 (attaching config files for brokers) 2)produce 5000 messages to broker1 using standard artemis client ./artemis producer --url tcp: //localhost:61616 --message-count 5000 3) Consume 100 messages using A-MQ 6 standard client attaching to broker2 java -jar /opt/a-mq-6/activemq-all.jar consumer --brokerUrl tcp: //localhost:61716 --user admin --password admin --destination TEST --messageCount 100 4) Consume 100 messages using A-MQ 6 standard client attaching to broker1 java -jar activemq-all-5.11.0.redhat-630187.jar consumer --brokerUrl tcp: //localhost:61616 --user admin --password admin --destination TEST --messageCount 100 Steps 3 and 4 force the messages to migrate across the network as expected. However after multiple interations of step 3 and step 4 in the JMX console the messages appear to be traversing the network in a quick continuous loop even when no consumer is attached to the brokers. NOTE: activemq-all-5.11.0.redhat-630187.jar is found in the jboss-a-mq-6.3.0.redhat-187/extras/apache-activemq-5.11.0.redhat-630187-bin.zip

      • Using a two broker statically configured cluster with message-load-balancing=ON_DEMAND and redistribution-delay=0 with an A-MQ6 openwire standard example consumers. (broker config files attached)
      • produced 5000 messages to broker1

      -The A-MQ6 consumer connects to broker2 consumes 100 messages and disconnects. The consumer then connects to broker1 consumes 100 messages and disconnects. Initial I see the messages move across the network after the demand (as expected) by observing the JMX MBeans for the destination on both brokers.

      Repeating the last step multiple times, periodically I see the messages keep traversing the network even when no consumers attached to either broker. It usually happens with 5 or 6 repetitions of the last step - but unfortunately it is not consistent.

      Note: When using the stardard artemis sample client, I have not been able to reproduce the issue.

        2. broker.xml
          6 kB
          Patrick Fox
        3. broker2.xml
          6 kB
          Patrick Fox

              gaohoward Howard Gao
              rhn-support-pfox Patrick Fox (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated:
                Resolved: