Uploaded image for project: 'JBoss Enterprise Application Platform'
  1. JBoss Enterprise Application Platform
  2. JBEAP-16640

Replicated journal - sometimes synchronization times out during failback

    XMLWordPrintable

Details

    • Bug
    • Resolution: Done
    • Critical
    • 7.2.3.CR1, 7.2.3.GA
    • 7.2.1.CR1
    • ActiveMQ
    • None
    • Hide

      Steps to reproduce:

      git clone git@gitlab.mw.lab.eng.bos.redhat.com:jbossqe-eap/messaging-testsuite.git
cd eap-tests-hornetq/scripts/
git checkout master

groovy -DEAP_ZIP_URL=https://eap-qe-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/eap-7.x-messaging-testing-prepare/712/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=ReplicatedDedicatedFailoverTestCase#testMultipleFailoverWithQueueKill     -Deap7.org.jboss.qa.hornetq.apps.clients.version=7.1553845118-SNAPSHOT | tee log
      Show
      Steps to reproduce: git clone git@gitlab.mw.lab.eng.bos.redhat.com:jbossqe-eap/messaging-testsuite.git cd eap-tests-hornetq/scripts/ git checkout master groovy -DEAP_ZIP_URL=https: //eap-qe-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/eap-7.x-messaging-testing-prepare/712/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=ReplicatedDedicatedFailoverTestCase#testMultipleFailoverWithQueueKill -Deap7.org.jboss.qa.hornetq.apps.clients.version=7.1553845118-SNAPSHOT | tee log

    Description

      Test Scenario:

      • Start two servers in replicated dedicated HA topology
      • Start producer and receiver sending/receiving messages to queue
      • 50 times kill and start live so clients failover/failback
      • Stop producer and wait for reciever to consume all messages

      Expected result:
      Number of send and received messages is the same after test.

      Actual result:
      Sometimes happens that during failback (live starting) synchronization between live and backup times out and live does not start again.

      Customer impact:
      Automatic failback may not happen and manual intervention is required to return environment to original state.

      Workaround: Stop/Kill live server and try to start again.

      Attaching trace logs from all servers and clients.

      Attachments

        Issue Links

          is cloned by

          Bug - A problem that impairs or prevents the functions of the product. ENTMQBR-2390 Replicated journal - sometimes synchronization times out during failback

          • Critical - To be worked on immediately following BLOCKER issues.
          • Closed

          Activity

            People

              rhn-support-jbertram Justin Bertram
              mnovak1@redhat.com Miroslav Novak
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: