9:30 a.m.
[
https://issues.jboss.org/browse/WFLY-6781?page=com.atlassian.jira.plugin....
]
Paul Ferraro commented on WFLY-6781:
------------------------------------
I'm confused, as you seem to be using the terms RC and SL to interchangeably refer to
web applications (e.g. RC.war and SL.rar) and a mysterious component with a remoting
connection (e.g. RC communicates remotely with SL). What kind of component is this? How
is the remoting connection used?
server-host1-RC and server-host1-SL belong to different server groups - but I don't
know how these server groups are configured.
You seem to be managing the server instance of each node as its own domain, is that right?
Why is that? How do the configurations of these domains differ?
"By the way RC communicates remotely with SL using the below url :
http-remoting://<ip address of SL which is Node1>:6080/"
What is the context in which this url is used? Is this a JNDI provider URL? Details
please.
Remoting connections are point-to-point connections and don't magically failover if
the target location becomes unavailable. What exactly is your expectation here?
I still don't understand exactly what aspect of your system is "clustered".
I also don't understand which connections you expect to failover. Which (and what
kind of) components are clustered? Do your logs indicate proper cluster formation? What
do your logs indicate when you test these failure scenarios?
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: Clustering
Affects Versions: 8.2.0.Final
Reporter: Preeta Kuruvilla
Assignee: Paul Ferraro
Priority: Blocker
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)
3121
days inactive
3121
days old
0 comments
1 participants
participants (1)
-
Paul Ferraro (JIRA)