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

Live does not become active after failback in colocated replicated toplogy

    XMLWordPrintable

    Details

    • Target Release:
    • Steps to Reproduce:
      Hide 

      git clone git://git.app.eng.bos.redhat.com/jbossqe/eap-tests-hornetq.git
      		 
      cd eap-tests-hornetq/scripts/
      		 
      git checkout refactoring_modules
      		 
      groovy -DEAP_VERSION=7.0.0.ER7 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
      		 
      export JOURNAL_DIRECTORY_A=$WORKSPACE/journal-A
      		 
      export JOURNAL_DIRECTORY_B=$WORKSPACE/journal-B
      		 
      export JOURNAL_DIRECTORY_C=$WORKSPACE/journal-C
      		 
      export JOURNAL_DIRECTORY_D=$WORKSPACE/journal-D
      		 
       
      		 
      cd ../jboss-hornetq-testsuite/
      		 
       
      		 
      mvn clean test -Dtest=ReplicatedColocatedClusterFailoverTestCase#testFailbackTransAckTopic -DfailIfNoTests=false -Deap=7x | tee log

      You have to replace artemis jars with newer. You can build it from https://github.com/rh-messaging/jboss-activemq-artemis. Use 992a044f6ff2e39eb00818a380f4c6f52ebc747b commit.

      Note: This is an intermittent issue, you have to run several times to hit it. You can use repeat_test_until_fail.sh script which is located in messaging test suite in jboss-hornetq-testsuite directory.

      Show
      git clone git://git.app.eng.bos.redhat.com/jbossqe/eap-tests-hornetq.git cd eap-tests-hornetq/scripts/ git checkout refactoring_modules groovy -DEAP_VERSION=7.0.0.ER7 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 export JOURNAL_DIRECTORY_A=$WORKSPACE/journal-A export JOURNAL_DIRECTORY_B=$WORKSPACE/journal-B export JOURNAL_DIRECTORY_C=$WORKSPACE/journal-C export JOURNAL_DIRECTORY_D=$WORKSPACE/journal-D   cd ../jboss-hornetq-testsuite/   mvn clean test -Dtest=ReplicatedColocatedClusterFailoverTestCase#testFailbackTransAckTopic -DfailIfNoTests=false -Deap=7x | tee log You have to replace artemis jars with newer. You can build it from https://github.com/rh-messaging/jboss-activemq-artemis . Use 992a044f6ff2e39eb00818a380f4c6f52ebc747b commit. Note: This is an intermittent issue, you have to run several times to hit it. You can use repeat_test_until_fail.sh script which is located in messaging test suite in jboss-hornetq-testsuite directory.
    • Affects:
      Release Notes
    • Release Notes Docs Status:
      Documented as Known Issue
    • Sprint:
      EAP 7.0.1

      Description

      Scenario: We have two nodes configured in replicated colocated HA topology. Each node contains two Artemis servers, one live and one backup.

      • Start both nodes
      • Start sending large messages to inQueue on node 1 and receiving them from inQueue on node 1
      • During sending and receiving kill node 1
      • Producer and subscriber make failover on backup and continue in sending and receiving messages
      • After producer sends 500 messages start node-1 again and wait for failback

      Expectation: Receiver get all sent messages, none of clients gets any exception, failback was successful

      Actual state: Sometimes live server on node 1 does not become active after failback.

      Customer impact: After failback both live and backup are deactivated and clients cannot connect to any server.

        Gliffy Diagrams

          Attachments

          1. issue-2-node-1.log
            125 kB
          2. issue-2-node-2.log
            119 kB
          3. issue-2-test.log
            4.04 MB
          4. node-1.log
            98 kB
          5. node-1-thread-dump.txt
            140 kB
          6. node-2.log
            126 kB

            Issue Links

            causes

            Sub-task - The sub-task of the issue JBEAP-4453 Document JBEAP-3998 for RN

            • Major - A request that should be considered seriously but is not a show stopper.
            • Closed
            is incorporated by

            Component Upgrade - A task tracking an update to a bundled component JBEAP-4615 Upgrade Artemis from 1.1.0.SP16 to 1.1.0.SP17

            • Blocker - An issue (bug, feature, task) that blocks development and/or testing work, production could not run. An upcoming version that is affected by this issue cannot be released until it's addressed.
            • Closed
            relates to

            Task - A task that needs to be done. JBEAP-5245 Docs: Remove JBEAP-3998 and associated fixed JIRAs from 7.0.1 RNs

            • Major - A request that should be considered seriously but is not a show stopper.
            • Closed

              Activity

                People

                • Assignee:
                  martyn-taylor Martyn Taylor
                  Reporter:
                  eduda Erich Duda
                • Votes:
                  0 Vote for this issue
                  Watchers:
                  13 Start watching this issue

                  Dates

                  • Created:
                    Updated:
                    Resolved: