11:06 a.m.
[
https://issues.jboss.org/browse/WFLY-6781?page=com.atlassian.jira.plugin....
]
Preeta Kuruvilla edited comment on WFLY-6781 at 6/30/16 12:05 PM:
------------------------------------------------------------------
Attached are the logs before and after incorporating the failover testing scenario for
both RC and SL.
BeforeFailover logs : Are when Node1 and Node2 are running and working correctly and JMS
messages is processed.
AfterFailover logs: Are when Node2 is powered off and Node1 is running but JMS messages on
Node1 is not getting processed by SL on Node1.
Note : The workaround we have found is to restart both Node1 and Node2. Just powering on
Node2 is not enough to make it work as expected.
[^attachment-name.zip]
was (Author: kpreeta12):
Attached are the logs before and after testing failover for both RC and SL.
BeforeFailover logs : Are when Node1 and Node2 are running and working correctly and JMS
messages is processed.
AfterFailover logs: Are when Node2 is powered off and Node1 is running but JMS messages on
Node1 is not getting processed by SL on Node1.
Note : The workaround we have found is to restart both Node1 and Node2. Just powering on
Node2 is not enough to make it work as expected.
[^attachment-name.zip]
Wildfly cluster's failover functionality doesn't work as
expected
-----------------------------------------------------------------
Key: WFLY-6781
URL: https://issues.jboss.org/browse/WFLY-6781
Project: WildFly
Issue Type: Bug
Components: JMS
Affects Versions: 8.2.0.Final
Reporter: Preeta Kuruvilla
Assignee: Jeff Mesnil
Priority: Blocker
Attachments: domain.Node1.xml, host.Node1.xml, host.Node2.xml,
server.RC.Node1.AfterFailover.log, server.RC.Node1.BeforeFailover.log,
server.RC.Node2.AfterFailover.log, server.RC.Node2.BeforeFailover.log,
server.SL.Node1.AfterFailover.log, server.SL.Node1.BeforeFailover.log
Following are the testing scenarios we did and the outcome:-
1. Network disabling on a VM for testing failover – Not working for both Linux and
Windows environment.
2. Power off of a VM using VMware client for testing failover – Is working on Linux
environment but not working on windows environment.
3. Ctrl + C method to stop services on a node for testing failover – works on both linux
and windows environment
4. Stopping server running on Node /VM using Admin Console for testing failover - works
on both linux and windows environment.
Jgroups subsystem configuration in domain.xml we have is below:-
<subsystem xmlns="urn:jboss:domain:jgroups:2.0"
default-stack="udp">
<stack name="udp">
<transport type="UDP"
socket-binding="jgroups-udp"/>
<protocol type="PING"/>
<protocol type="MERGE3"/>
<protocol type="FD_SOCK"
socket-binding="jgroups-udp-fd"/>
<protocol type="FD_ALL"/>
<protocol type="VERIFY_SUSPECT"/>
<protocol type="pbcast.NAKACK2"/>
<protocol type="UNICAST3"/>
<protocol type="pbcast.STABLE"/>
<protocol type="pbcast.GMS"/>
<protocol type="UFC"/>
<protocol type="MFC"/>
<protocol type="FRAG2"/>
<protocol type="RSVP"/>
</stack>
<stack name="tcp">
<transport type="TCP"
socket-binding="jgroups-tcp"/>
<protocol type="MPING"
socket-binding="jgroups-mping"/>
<protocol type="MERGE2"/>
<protocol type="FD_SOCK"
socket-binding="jgroups-tcp-fd"/>
<protocol type="FD"/>
<protocol type="VERIFY_SUSPECT"/>
<protocol type="pbcast.NAKACK2"/>
<protocol type="UNICAST3"/>
<protocol type="pbcast.STABLE"/>
<protocol type="pbcast.GMS"/>
<protocol type="MFC"/>
<protocol type="FRAG2"/>
<protocol type="RSVP"/>
</stack>
</subsystem>
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
3101
days inactive
3101
days old
0 comments
1 participants
participants (1)
-
Preeta Kuruvilla (JIRA)