WildFly HornetQ Collocated Message Replication-Based HA and Load Balancing Configuration: Difference between revisions
Jump to navigation
Jump to search
(Created page with "=Internal= =Overview= It is an overlay of two procedures. Start with [[]]. Then apply [[]] in top of it. Example of working Amazon EC2 two-node cluster configuration fil...") |
|||
| (19 intermediate revisions by the same user not shown) | |||
| Line 1: | Line 1: | ||
=Internal= | =Internal= | ||
* [[WildFly HornetQ-Based Messaging Subsystem Configuration|HornetQ-Based Messaging Configuration]] | |||
* [[WildFly_HornetQ-Based_Messaging_Subsystem_Concepts#Collocated_Topology_with_Message_Replication.2C_no_Load_Balancing|HornetQ-Based Messaging Subsystem Concepts]] | |||
* [[WildFly HornetQ Collocated Message-Replication Based HA Configuration|Collocated Topology with Message Replication]] | |||
* [[WildFly HornetQ-Based Messaging Subsystem - Clustering with TCP|TCP-Based Clustering Configuration]] | |||
=Overview= | =Overview= | ||
It is an overlay of two procedures | It is an overlay of the following two procedures: | ||
Start with [[]]. | Start with [[WildFly HornetQ Collocated Message-Replication Based HA Configuration|Collocated Topology with Memory Replication]]. | ||
Then apply [[]] in top of it. | Then apply [[WildFly HornetQ-Based Messaging Subsystem - Clustering with TCP|TCP-Based Clustering Configuration]] in top of it. | ||
Example of working Amazon EC2 two-node cluster configuration files: | =Local Example - Two JBoss Instances on the Same VM= | ||
* [[]] | |||
* [[]] | Example of relevant parts of a working local two-node cluster configuration files. Both JBoss instances run on the same host, and the second node must be started with a port offset of 200. This example was extensively tested: | ||
* [[EAP 6.4 Configuration File - HornetQ Node A Message Replication Collocated HA and Load Balancing standalone-full.xm - Same VMl|node A standalone-full.xml]] | |||
* [[EAP 6.4 Configuration File - HornetQ Node B Message Replication Collocated HA and Load Balancing standalone-full.xm - Same VMl|node B standalone-full.xml]] | |||
Diagram: | |||
<blockquote style="background-color: #f9f9f9; border: solid thin lightgrey;"> | |||
:[[WildFly HornetQ Collocated Message Replication-Based HA and Load Balancing Diagram|Diagram]] | |||
</blockquote> | |||
The actual working configuration files: | |||
<blockquote style="background-color: AliceBlue; border: solid thin LightSteelBlue;"> | |||
:https://github.com/NovaOrdis/playground/tree/master/jboss/hornetq/collocated-message-replication-HA-with-load-balancing<br> | |||
</blockquote> | |||
=Amazon EC2 Example - Two Different VMs= | |||
Example of relevant parts of a working Amazon EC2 two-node cluster configuration files: | |||
* [[EAP 6.4 Configuration File - HornetQ Node A Message Replication Collocated HA and Load Balancing standalone-full.xml|node A standalone-full.xml]] | |||
* [[EAP 6.4 Configuration File - HornetQ Node B Message Replication Collocated HA and Load Balancing standalone-full.xml|node B standalone-full.xml]] | |||
Latest revision as of 00:20, 4 June 2016
Internal
- HornetQ-Based Messaging Configuration
- HornetQ-Based Messaging Subsystem Concepts
- Collocated Topology with Message Replication
- TCP-Based Clustering Configuration
Overview
It is an overlay of the following two procedures:
Start with Collocated Topology with Memory Replication.
Then apply TCP-Based Clustering Configuration in top of it.
Local Example - Two JBoss Instances on the Same VM
Example of relevant parts of a working local two-node cluster configuration files. Both JBoss instances run on the same host, and the second node must be started with a port offset of 200. This example was extensively tested:
Diagram:
The actual working configuration files:
Amazon EC2 Example - Two Different VMs
Example of relevant parts of a working Amazon EC2 two-node cluster configuration files: