8:15 p.m.
[
https://issues.jboss.org/browse/WFLY-6781?page=com.atlassian.jira.plugin....
]
Preeta Kuruvilla edited comment on WFLY-6781 at 7/4/16 2:14 PM:
----------------------------------------------------------------
As per your suggestion,
I have tried setting <connection-ttl>60000</connection-ttl> in configuration
of RemoteConnectionFactory.
When I do this, even without doing any failover testing , the SL(JMS) is not able to
process any request. The status of these request is "processing" for ever.
It might mean that connection has timed out before processing with this setting. Also
would like to remind you that the failover by power off method works properly on Linux.
Only its got issues (probably JMS related) on Windows OS.
Thanks,
Preeta
was (Author: kpreeta12):
As per your suggestion,
I have tried setting <connection-ttl>60000</connection-ttl> in configuration
of RemoteConnectionFactory.
When I do this, even without doing any failover testing , the SL(JMS) is not able to
process any request. The status of these request is "processing" for ever.
It might mean that connection has timed out before processing with this setting.
Thanks,
Preeta
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)
3106
days inactive
3106
days old
0 comments
1 participants
participants (1)
-
Preeta Kuruvilla (JIRA)