Uploaded image for project: 'A-MQ Broker'
  1. A-MQ Broker
  2. ENTMQBR-1182

Lost message when MDB is resending messages under high load

    Details

    • Type: Bug
    • Status: Done
    • Priority: Blocker
    • Resolution: Done
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: None
    • Target Release:
    • Sprint:
      AMQ Broker 1833
    • Steps to Reproduce:
      Hide

      Steps to reproduce: Problem is happening randomly - this is intermittent fail

      git clone git://git.app.eng.bos.redhat.com/jbossqe/eap-tests-hornetq.git
      cd eap-tests-hornetq/scripts/
      git checkout f09a8d81993d335f67e7e1de044e2cc68e45564c
      
      groovy -DEAP_ZIP_URL=https://eap-qe-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/early-testing-messaging-prepare/268//artifact/jboss-eap.zip PrepareServers7.groovy
      export WORKSPACE=$PWD
      export JBOSS_HOME_1=$WORKSPACE/server1/jboss-eap
      export JBOSS_HOME_2=$WORKSPACE/server2/jboss-eap
      export JBOSS_HOME_3=$WORKSPACE/server3/jboss-eap
      export JBOSS_HOME_4=$WORKSPACE/server4/jboss-eap
      cd ../jboss-hornetq-testsuite/
      mvn clean test -Dtest=Lodh5DoubleSendToDbTestCase#testORACLE11GR2MdbCpuNormalMessages -Deap7.org.jboss.qa.hornetq.apps.clients.version=7.1520950239-SNAPSHOT -DfailIfNoTests=false | tee log
      
      Show
      Steps to reproduce: Problem is happening randomly - this is intermittent fail git clone git: //git.app.eng.bos.redhat.com/jbossqe/eap-tests-hornetq.git cd eap-tests-hornetq/scripts/ git checkout f09a8d81993d335f67e7e1de044e2cc68e45564c groovy -DEAP_ZIP_URL=https: //eap-qe-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/early-testing-messaging-prepare/268//artifact/jboss-eap.zip PrepareServers7.groovy export WORKSPACE=$PWD export JBOSS_HOME_1=$WORKSPACE/server1/jboss-eap export JBOSS_HOME_2=$WORKSPACE/server2/jboss-eap export JBOSS_HOME_3=$WORKSPACE/server3/jboss-eap export JBOSS_HOME_4=$WORKSPACE/server4/jboss-eap cd ../jboss-hornetq-testsuite/ mvn clean test -Dtest=Lodh5DoubleSendToDbTestCase#testORACLE11GR2MdbCpuNormalMessages -Deap7.org.jboss.qa.hornetq.apps.clients.version=7.1520950239-SNAPSHOT -DfailIfNoTests= false | tee log

      Description

      Test scenario:

      • Start cluster A of nodes node-1, node-3
      • Start cluster B of nodes node-2, node-4
      • Send messages to queue on node-1
      • Deploy mdbs to servers in cluster A. This mdb reads messages from local queue, sends them to remote queue on cluster B and inserts them into database
      • Deploy mdbs to servers in cluster B. This mdb reads messages from local queue and inserts them into database
      • Cause CPU overload (for 5 min) on server node-2 when mdbs on cluster1 and 2 are processing mesages
      • Restart failed server
      • Let MDBs to process remaining messages

      Pass Criteria: Number of sent message is equal number of records(lines) in database and messages in

      Actual Result:
      Sometimes happens that one record is missing in database which means that one message was not processed be MDB in cluster 2.

      This looks like broker related regression against Artemis 1.5.
      Wildfly: https://github.com/jmesnil/wildfly/tree/WFLY-9407_upgrade_artemis_2.4.0_with_prefix (06c878a313d3cad323889d017e60fd5533204d1a)
      Artemis tag 2.5.0.Final

        Gliffy Diagrams

          Attachments

            Issue Links

              Activity

                People

                • Assignee:
                  martyn-taylor Martyn Taylor
                  Reporter:
                  mnovak Miroslav Novak
                  Tester:
                  Michal Toth
                • Votes:
                  0 Vote for this issue
                  Watchers:
                  3 Start watching this issue

                  Dates

                  • Created:
                    Updated:
                    Resolved:

                    Time Tracking

                    Estimated:
                    Original Estimate - 2 days
                    2d
                    Remaining:
                    Remaining Estimate - 2 days
                    2d
                    Logged:
                    Time Spent - Not Specified
                    Not Specified