4a5af776d8
Implement Federated Queue (builds on recent consumer priority) Implement Federated Address (builds on recent queue level auto-delete) Add Functional Tests Add Failure Tests (remote and local shutdowns) Add Documentation |
||
|---|---|---|
| .. | ||
| src/main | ||
| eu-west-east-us-central.png | ||
| pom.xml | ||
| readme.md | ||
readme.md
Federated Address Example
To run the example, simply type mvn verify from this directory, or mvn -PnoServer verify if you want to start and create the broker manually.
This example demonstrates a core multicast address deployed on three different brokers. The three brokers are configured to form a federated address mesh.
In the example we name the brokers, eu-west, eu-east and us-central to give an idea of the use case.
The following is then carried out:
-
create a consumer on the queue on each node, and we create a producer on only one of the nodes.
-
send some messages via the producer on EU West, and we verify that all the consumers receive the sent messages, in essence multicasting the messages within and accross brokers.
-
Next then verify the same on US Central.
-
Next then verify the same on EU East.
In other words, we are showing how with Federated Address, ActiveMQ Artemis replicates sent messages to all addresses and subsequently delivered to all all consumers, regardless if the consumer is local or is on a distant broker. Decoupling the location where producers and consumers need to be.
The config that defines the federation you can see in the broker.xml for each broker is within the following tags. You will note upstreams are different in each as well as the federation name, which has to be globally unique.
<federations>
...
</federations>
For more information on ActiveMQ Artemis Federation please see the federation section of the user manual.