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

Broker displays incorrect message count after failback

    XMLWordPrintable

Details

    • Bug
    • Resolution: Not a Bug
    • Major
    • None
    • AMQ 7.7.0.GA
    • broker-core
    • None
    • Hide

      There is a test-case.zip attached to JIRA. This is simple reproducer, unzip it and run " mvn package" command to build it. In the resources directory there are two files broker.xml.master and broker.xml.slave. Use those to start your master and backup brokers. You may need to edit them and change the host name.

      Before running reproducer edit the jndi.properties file and modify the host name used in your tests. To run use command "mvn exec:java". The reproducer creates 10 durable susbscribers on a topic called testTopic. Two of those subscribers are slow with message processing.

      Start master broker followed by back broker using configuration provided.

      Once they are running start the reproducer and wait until all subscribers are created. Then using load generator start publishing messages on master broker to testTopic. Wait until you see in master log file that the testTopic started paging. Few few minutes more then "kill -9" master broker. Using cli query the testTopic stats they should show number that don't make sense. After 5 minutes performa fail back by restarting master and again using cli query stats for tesTopic.

       

       

      Show
      There is a test-case.zip attached to JIRA. This is simple reproducer, unzip it and run " mvn package" command to build it. In the resources directory there are two files broker.xml.master and broker.xml.slave. Use those to start your master and backup brokers. You may need to edit them and change the host name. Before running reproducer edit the jndi.properties file and modify the host name used in your tests. To run use command "mvn exec:java". The reproducer creates 10 durable susbscribers on a topic called testTopic. Two of those subscribers are slow with message processing. Start master broker followed by back broker using configuration provided. Once they are running start the reproducer and wait until all subscribers are created. Then using load generator start publishing messages on master broker to testTopic. Wait until you see in master log file that the testTopic started paging. Few few minutes more then "kill -9" master broker. Using cli query the testTopic stats they should show number that don't make sense. After 5 minutes performa fail back by restarting master and again using cli query stats for tesTopic.    

    Description

      An address with 3 subscribers (all paging), one of them a slow subscriber, displays incorrect message count for the fast subscribers after failback. The error gets corrected only after the slow subscriber finishes processing all it messages and stops paging.

      Attachments

        Activity

          People

            csuconic@redhat.com Clebert Suconic
            rhn-support-toross Tom Ross
            Votes:
            0 Vote for this issue
            Watchers:
            7 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: