Status: Resolved (View Workflow)
git clone git: //git.app.eng.bos.redhat.com/jbossqe/eap-tests-hornetq.git cd eap-tests-hornetq/scripts/ groovy -DEAP_ZIP_URL=https: //eap-qe-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/early-testing-messaging-prepare/265/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#testFailbackWithDivertsTransAckQueueKill -DfailIfNoTests= false -Deap=7x -Deap7.org.jboss.qa.hornetq.apps.clients.version=7.1521544306-SNAPSHOT | tee log
Across all replicated HA tests I often see an issue that initial synchronization between Live and Backup was not triggered.
- There are two Wildfly servers configured as replicated Live-Backup pair.
- Live server is killed/shutdown
Expectation: Backup server becomes active.
Reality: Backup server does not become active, because initial synchronization with Live server was not triggered.
Users impact: Replicated HA feature doesn't work properly.
Blocker priority was set because this is regression against previous Wildfly releases.
Detail description of the issue
In the trace log there is last message from the SharedNothingBackupActivation which says that it is waiting on cluster connection. It is interested that JGroups subsystem is booting after this message was logged. However I am not sure if this could cause the issue.