Status: Closed (View Workflow)
Steps to Reproduce:
The test passes even if the issue is present. You have to check server logs whether the issue is present or not.The test passes even if the issue is present. You have to check server logs whether the issue is present or not. 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=... 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=DedicatedFailoverTestCase#testMultipleFailoverWithQueueShutdown -Deap7.org.jboss.qa.hornetq.apps.clients.version=7.1533784013-SNAPSHOT -DfailIfNoTests= false -Deap=7x | tee log
- There are two Wildfly servers configured in messaging dedicated shared store HA topology
- Live server is several times killed and restarted
- Test checks that clients do failover/failback
When the backup server gets activated it logs several NullPointerExceptions.
The NPE has not functional impact in our scenario but it can have in different scenarios.
Blocker priority was chosen because this is regression against WF 13.