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

(7.2.z) ENTMQBR-2049 - Sometimes Artemis cluster with JGroups discovery is not formed after restart

    XMLWordPrintable

Details

    • Bug
    • Resolution: Won't Do
    • Critical
    • 7.2.10.GA
    • 7.2.0.CD14, 7.2.0.GA, 7.2.1.CR1
    • JMS
    • None
    • Workaround Exists
    • Hide

      Node which did not join Artemis cluster must be re-started.

      Show
      Node which did not join Artemis cluster must be re-started.
    • Hide

      Adding steps to reproduce, issue was intermittent:

      git clone git://git.app.eng.bos.redhat.com/jbossqe/eap-tests-hornetq.git
cd eap-tests-hornetq/scripts/
git checkout eap7.2.x-artemis2.x-ha-jdbc
groovy -DEAP_ZIP_URL=https://mw-messaging-qe-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/EAP-tooling/job/early-testing-messaging-prepare/155/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=RemoteJcaRebalancingTestCase#testLoadBalancingOfInboundConnectionsToClusterOneServerRestart  -Deap7.org.jboss.qa.hornetq.apps.clients.version=7.1531748885-SNAPSHOT -Dprepare.param.DATABASE=oracle12cR2 -Dprepare.param.JDBC_STORE=true | tee log
      Show
      Adding steps to reproduce, issue was intermittent: git clone git: //git.app.eng.bos.redhat.com/jbossqe/eap-tests-hornetq.git cd eap-tests-hornetq/scripts/ git checkout eap7.2.x-artemis2.x-ha-jdbc groovy -DEAP_ZIP_URL=https: //mw-messaging-qe-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/EAP-tooling/job/early-testing-messaging-prepare/155/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=RemoteJcaRebalancingTestCase#testLoadBalancingOfInboundConnectionsToClusterOneServerRestart -Deap7.org.jboss.qa.hornetq.apps.clients.version=7.1531748885-SNAPSHOT -Dprepare.param.DATABASE=oracle12cR2 -Dprepare.param.JDBC_STORE= true | tee log

    Description

      Sometimes happens there are undelivered messages in scenario with servers in remote JCA topology are restarted. The problem is that messages are not redistributed to node with consumer because Artemis cluster was not formed restart. Issue is very intermittent and hard to hit especially with enabled traces.

      Impact for the customer: Restarted node in Artemis cluster might not join cluster again. Server(s) in cluster must be restarted so cluster is formed correctly.

      Test scenario:

      • Start 2 server in Artemis cluster
      • Start 2 servers with MDB connected to Artemis cluster
        • MDB resends messages from InQueue to OutQueue from/to remote cluster
      • Send messages to InQueue
      • Restart all server (one by one)
      • Consumes messages from OutQueue

      Results:
      After the test there are undelivered messages.

      This issue is regression against EAP 7.1 and EAP 7.2.0.CD13.

      Attachments

        Issue Links

          clones

          Bug - A problem that impairs or prevents the functions of the product. WFLY-11029 Sometimes Artemis cluster with JGroups discovery is not formed after restart

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Reopened
          is cloned by

          Bug - A problem that impairs or prevents the functions of the product. JBEAP-18324 (7.3.z) ENTMQBR-2049 - Sometimes Artemis cluster with JGroups discovery is not formed after restart

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

          Bug - A problem that impairs or prevents the functions of the product. ENTMQBR-2049 Sometimes Artemis cluster with JGroups discovery is not formed after restart

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed

          Activity

            People

              rh-ee-ataylor Andy Taylor
              mnovak1@redhat.com Miroslav Novak
              Votes:
              0 Vote for this issue
              Watchers:
              13 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: