HornetQ Deploying a Distributed Topic: Difference between revisions
Jump to navigation
Jump to search
(Created page with "=Internal= * WildFly Messaging Subsystem Configuration") |
|||
| Line 2: | Line 2: | ||
* [[WildFly HornetQ-Based Messaging Subsystem Configuration#Subjects|WildFly Messaging Subsystem Configuration]] | * [[WildFly HornetQ-Based Messaging Subsystem Configuration#Subjects|WildFly Messaging Subsystem Configuration]] | ||
=Overview= | |||
This article explains how to deploy a distributed topic - meaning that messages are internally distributed amongst the HornetQ nodes that have the topic deployed on them. The underlying cluster connection that does the internal message distribution is configured to only handle messages destined to the specific topic we're distributing, maintaining all other destinations isolated. | |||
The example assumes three nodes (n1, n2 and n3). | |||
Revision as of 01:05, 25 May 2016
Internal
Overview
This article explains how to deploy a distributed topic - meaning that messages are internally distributed amongst the HornetQ nodes that have the topic deployed on them. The underlying cluster connection that does the internal message distribution is configured to only handle messages destined to the specific topic we're distributing, maintaining all other destinations isolated.
The example assumes three nodes (n1, n2 and n3).