2:04 a.m.
[
https://issues.jboss.org/browse/WFLY-6781?page=com.atlassian.jira.plugin....
]
Preeta Kuruvilla commented on WFLY-6781:
----------------------------------------
Thanks Paul.
Below is the messaging subsystem declared in the domain.xml.
{color:#205081}<profile name="ha">
<subsystem xmlns="urn:jboss:domain:messaging:2.0">
<hornetq-server>
<security-enabled>false</security-enabled>
<journal-file-size>102400</journal-file-size>
<connectors>
<http-connector name="http-connector"
socket-binding="remote-http">
<param key="http-upgrade-endpoint"
value="http-acceptor"/>
</http-connector>
<http-connector name="http-connector-throughput"
socket-binding="http">
<param key="http-upgrade-endpoint"
value="http-acceptor-throughput"/>
<param key="batch-delay"
value="50"/>
</http-connector>
<in-vm-connector name="in-vm"
server-id="0"/>
</connectors>
<acceptors>
<http-acceptor http-listener="default"
name="http-acceptor"/>
<http-acceptor http-listener="default"
name="http-acceptor-throughput">
<param key="batch-delay"
value="50"/>
<param key="direct-deliver"
value="false"/>
</http-acceptor>
<in-vm-acceptor name="in-vm"
server-id="0"/>
</acceptors>
<security-settings>
<security-setting match="#">
<permission type="send" roles="jmsrole
guest"/>
<permission type="consume" roles="jmsrole
guest"/>
<permission type="createDurableQueue"
roles="jmsrole"/>
<permission type="deleteDurableQueue"
roles="jmsrole"/>
<permission type="createNonDurableQueue"
roles="guest"/>
<permission type="deleteNonDurableQueue"
roles="guest"/>
</security-setting>
</security-settings>
<address-settings>
<address-setting match="#">
<dead-letter-address>jms.queue.DLQ</dead-letter-address>
<expiry-address>jms.queue.ExpiryQueue</expiry-address>
<redelivery-delay>0</redelivery-delay>
<max-size-bytes>10485760</max-size-bytes>
<address-full-policy>BLOCK</address-full-policy>
<message-counter-history-day-limit>10</message-counter-history-day-limit>
</address-setting>
</address-settings>
<jms-connection-factories>
<connection-factory name="InVmConnectionFactory">
<connectors>
<connector-ref connector-name="in-vm"/>
</connectors>
<entries>
<entry name="/ConnectionFactory"/>
</entries>
</connection-factory>
<connection-factory
name="RemoteConnectionFactory">
<connectors>
<connector-ref
connector-name="http-connector"/>
</connectors>
<entries>
<entry
name="jms/RemoteConnectionFactory"/>
<entry
name="jboss/exported/jms/RemoteConnectionFactory"/>
</entries>
<connection-ttl>-1</connection-ttl>
<reconnect-attempts>-1</reconnect-attempts>
</connection-factory>
<pooled-connection-factory name="hornetq-ra">
<transaction mode="xa"/>
<connectors>
<connector-ref connector-name="in-vm"/>
</connectors>
<entries>
<entry name="/JmsXA"/>
<entry
name="jboss/DefaultJMSConnectionFactory"/>
</entries>
</pooled-connection-factory>
</jms-connection-factories>
<jms-destinations>
<jms-queue name="testQueue">
<entry name="queue/test"/>
<entry name="jboss/exported/jms/queue/test"/>
</jms-queue>
<jms-queue name="ISEEOutboundQueue">
<entry name="jms/ISEEOutboundQueue"/>
<entry
name="jboss/exported/jms/queue/ISEEOutboundQueue"/>
</jms-queue>
<jms-queue name="ISEEInboundQueue">
<entry name="jms/ISEEInboundQueue"/>
<entry
name="jboss/exported/jms/queue/ISEEInboundQueue"/>
</jms-queue>
<jms-queue name="BEEEAuthorizationsQueue">
<entry name="jms/BEEEAuthorizationsQueue"/>
<entry
name="jboss/exported/jms/queue/BEEEAuthorizationsQueue"/>
</jms-queue>
<jms-queue name="BEEERequisitionsQueue">
<entry name="jms/BEEERequisitionsQueue"/>
<entry
name="jboss/exported/jms/queue/BEEERequisitionsQueue"/>
</jms-queue>
<jms-queue name="BEEEInboundQueue">
<entry name="jms/BEEEInboundQueue"/>
<entry
name="jboss/exported/jms/queue/BEEEInboundQueue"/>
</jms-queue>
<jms-topic name="testTopic">
<entry name="topic/test"/>
<entry name="jboss/exported/jms/topic/test"/>
</jms-topic>
</jms-destinations>
</hornetq-server>
</subsystem>{color}
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
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)