WildFly HornetQ Collocated Message Replication-Based HA and Load Balancing Configuration: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
|||
| 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_In-Memory_Replication.2C_no_Load_Balancing|HornetQ-Based Messaging Subsystem Concepts]] | |||
* [[WildFly HornetQ In-Memory Collocated HA Configuration|Collocated Topology with In-Memory Replication]] | * [[WildFly HornetQ In-Memory Collocated HA Configuration|Collocated Topology with In-Memory Replication]] | ||
* [[WildFly HornetQ-Based Messaging Subsystem - Clustering with TCP|TCP-Based Clustering Configuration]] | * [[WildFly HornetQ-Based Messaging Subsystem - Clustering with TCP|TCP-Based Clustering Configuration]] | ||
Revision as of 03:15, 12 April 2016
Internal
- HornetQ-Based Messaging Configuration
- HornetQ-Based Messaging Subsystem Concepts
- Collocated Topology with In-Memory Replication
- TCP-Based Clustering Configuration
Overview
It is an overlay of two procedures.
Start with Collocated Topology with In-Memory Replication.
Then apply TCP-Based Clustering Configuration in top of it.
Example of working Amazon EC2 two-node cluster configuration files:
- [[]]
- [[]]