Status: Closed (View Workflow)
Affects Version/s: None
Fix Version/s: 11.0.0.Alpha1
Steps to Reproduce:git clone git: //git.app.eng.bos.redhat.com/jbossqe/eap-tests-hornetq.git cd eap-tests-hornetq/scripts/ git checkout 4e300f3ffa4a632506b4afb452eaf0405e0a64f5 groovy -DEAP_VERSION=7.1.0.DR9 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 cd ../jboss-hornetq-testsuite/ mvn clean test -Dtest=DedicatedFailoverTestCaseWithMdb#testKillWithFailback -DfailIfNoTests= false -Deap=7x -Deap7.org.jboss.qa.hornetq.apps.clients.version=7.1.0.DR9 | tee log
Remote JCA scenario:
- There are 3 nodes
- Node 1 and node 2 are Live-Backup pair (replicated HA)
- Node 3 has MDB which remotely connects to node 1 and is able to do failover on node 2
- During the test, node 1 is killed and started again
Problem occurs when node 1 is started again. Servers are configured to do failback. When node 1 wants to become live again, something goes wrong with connection between node 1 and node 2. On node 1 I can see repeated WARN message . Node 2 prints repeatedly WARN message .
I can see the same issue also with 7.0.x. We haven't notice this error because the test didn't check state of servers after the failback.
When I modify the test to not deploy MDB on node 3, the test passes without any unusual error. It seems the issue is related to this scenario.