-
Bug
-
Resolution: Done
-
Blocker
-
7.0.0.ER1
-
Regression
-
-
-
-
-
-
When I tried to do failback after failover in dedicated replicated topology, the master is neither activating nor announcing backup (I tried both configurations with and without allow-failback parameter).
Reproducer for scenario with allow-failback set on true
Prepare EAP servers
cd $WORKSPACE
wget http://download.eng.brq.redhat.com/devel/candidates/JBEAP/JBEAP-7.0.0.ER1/jboss-eap-7.0.0.ER1.zip
unzip jboss-eap-7.0.0.ER1.zip -d master
unzip jboss-eap-7.0.0.ER1.zip -d slave
cp /path/to/attached/master.xml $WORKSPACE/master/jboss-eap-7.0/standalone/configuration/standalone-full-ha.xml
cp /path/to/attached/slave.xml $WORKSPACE/slave/jboss-eap-7.0/standalone/configuration/standalone-full-ha.xml
chmod a+x $WORKSPACE/master/jboss-eap-7.0/bin/standalone.sh
chmod a+x $WORKSPACE/slave/jboss-eap-7.0/bin/standalone.sh
chmod a+x $WORKSPACE/master/jboss-eap-7.0/bin/jboss-cli.sh
Start master
$WORKSPACE/master/jboss-eap-7.0/bin/standalone.sh -c standalone-full-ha.xml
Start slave
$WORKSPACE/slave/jboss-eap-7.0/bin/standalone.sh -c standalone-full-ha.xml -Djboss.socket.binding.port-offset=1000
Now stop master and start it again. Finally check whether the master is active and the slave is not.
Check whether the master is active
$WORKSPACE/master/jboss-eap-7.0/bin/jboss-cli.sh -c "/subsystem=messaging-activemq/server=default/:read-attribute(name=active)"
Check whether the slave is active
$WORKSPACE/master/jboss-eap-7.0/bin/jboss-cli.sh -c --controller=localhost:10990 "/subsystem=messaging-activemq/server=default/:read-attribute(name=active)"
Expectation
- master is active
- slave is not active
Reality
- master is not active
- slave is active
- is blocked by
-
JBEAP-2211 Upgrade to Artemis 1.1.0.wildfly-009
-
- Closed
-
- relates to
-
-
- Closed
-
-
-
- Closed
-
