Wildfly 10.1 JMS cluster failover active active
mai_mostafa Mar 6, 2019 11:50 AMHow can I configure activemq artemis to resolve the following problem :
I have only two nodes in cluster that load balanced by apache and it works fine(I can see from admin page that messages go to both nodes) except jms queue
I want to use two nodes as "active active" not "master slave" and this what I did but if one node failed and its queue has messages ..I want these messages to be processed by other node.
How can I achieve it ?
here is a sample of standalone.xml
<subsystem xmlns="urn:jboss:domain:messaging-activemq:1.0">
<server name="default">
<cluster user="${jboss.messaging.cluster.user:test}" password="${jboss.messaging.cluster.password:test1}"/>
<security-setting name="#">
<role name="guest" send="true" consume="true" create-non-durable-queue="true" delete-non-durable-queue="true"/>
</security-setting>
<address-setting name="jms.queue.*" dead-letter-address="jms.queue.DLQ" expiry-address="jms.queue.ExpiryQueue" redelivery-delay="5000" max-delivery-attempts="-1" max-size-bytes="10485760"
page-size-bytes="2097152" message-counter-history-day-limit="10" redistribution-delay="1000"/>
<address-setting name="jms.queue.*.multiplyRedeliveryDelay" dead-letter-address="jms.queue.DLQ" expiry-address="jms.queue.ExpiryQueue" redelivery-delay="5000" redelivery-multiplier="2.0"
max-delivery-attempts="-1" max-redelivery-delay="3600000" max-size-bytes="10485760" page-size-bytes="2097152" message-counter-history-day-limit="10" redistribution-delay="1000"/>
<http-connector name="http-connector" socket-binding="http" endpoint="http-acceptor"/>
<http-connector name="http-connector-throughput" socket-binding="http" endpoint="http-acceptor-throughput">
<param name="batch-delay" value="50"/>
</http-connector>
<in-vm-connector name="in-vm" server-id="0"/>
<http-acceptor name="http-acceptor" http-listener="default"/>
<http-acceptor name="http-acceptor-throughput" http-listener="default">
<param name="batch-delay" value="50"/>
<param name="direct-deliver" value="false"/>
</http-acceptor>
<in-vm-acceptor name="in-vm" server-id="0"/>
<broadcast-group name="bg-group1" jgroups-channel="activemq-cluster" connectors="http-connector"/>
<discovery-group name="dg-group1" jgroups-channel="activemq-cluster" refresh-timeout="10000"/>
<cluster-connection name="my-cluster" address="jms" connector-name="http-connector" discovery-group="dg-group1"/>
<jms-queue name="ExpiryQueue" entries="java:/jms/queue/ExpiryQueue"/>
<jms-queue name="DLQ" entries="java:/jms/queue/DLQ"/>
<jms-queue name="AuditingQueue" entries="jms/queue/auditing java:jboss/exported/jms/queue/auditing"/>
<jms-queue name="AccountingCLMQueue.multiplyRedeliveryDelay" entries="jms/queue/accountingCLM java:jboss/exported/jms/queue/accountingCLM"/>
<connection-factory name="InVmConnectionFactory" entries="java:/ConnectionFactory" connectors="in-vm"/>
<connection-factory name="RemoteConnectionFactory" entries="java:jboss/exported/jms/RemoteConnectionFactory" connectors="http-connector" ha="true" block-on-acknowledge="true" reconnect-attempts="-1"/>
<pooled-connection-factory name="activemq-ra" entries="java:/JmsXA java:jboss/DefaultJMSConnectionFactory" connectors="http-connector" transaction="xa"/>
</server>
</subsystem>