History

Justin Bertram 9c459eb313 ARTEMIS-2413 upgrade JGroups JGroups 3.x hasn't been updated in some time now. The last release was in April 2020 almost 2 years ago. Lots of protocols have been updated and added and users are wanting to use them. There is also increasing concern about using older components triggered mainly by other recently-discovered high-profile vulnerabilities in the wider Open Source Java community. This commit bumps JGroups up to the latest release - 5.2.0.Final. However, there is a cost associated with upgrading. The old-style properties configuration is no longer supported. I think it's unlikely that end-users are leveraging this because it is not exposed via broker.xml. The JGroups XML configuration has been around for a long time, is widely adopted, and is still supported. I expect most (if not all) users are using this. However, a handful of tests needed to be updated and/or removed to deal with this absence. Some protocols and/or protocol properties are no longer supported. This means that users may have to change their JGroups stack configurations when they upgrade. For example, our own clustered-jgroups example had to be updated or it wouldn't run properly.		2022-02-04 13:47:11 -05:00
..
src/main	ARTEMIS-2413 upgrade JGroups	2022-02-04 13:47:11 -05:00
pom.xml	[maven-release-plugin] prepare for next development iteration	2021-12-14 22:50:55 -05:00
readme.md	ARTEMIS-1562 Refactor example documentation	2017-12-15 14:54:16 +00:00

readme.md

ActiveMQ Artemis Clustering with JGroups 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 the working of a two node cluster using JGroups as the underlying topology broadcasting/discovery technique.

We deploy a queue on to the cluster, then create a consumer on the queue on each node, and we create a producer on only one of the nodes.

We then send some messages via the producer, and we verify that both consumers receive the sent messages in a round-robin fashion.

This example uses JNDI to lookup the JMS Queue and ConnectionFactory objects. If you prefer not to use JNDI, these could be instantiated directly.

To enable ActiveMQ Artemis to use JGroups you need to configure JGroups configuration file and make sure it is on the classpath by placing in the configuration directory, the file test-jgroups-file_ping.xml is the configuration used in this exaample

You then configure the jgroups file used by the broadcast and discovery groups in the configuration along with the channel name which you want this cluster to share.

<broadcast-groups>
   <broadcast-group name="my-broadcast-group">
      <broadcast-period>5000</broadcast-period>
      <jgroups-file>test-jgroups-file_ping.xml</jgroups-file>
      <jgroups-channel>activemq_broadcast_channel</jgroups-channel>
      <connector-ref>netty-connector</connector-ref>
   </broadcast-group>
</broadcast-groups>

<discovery-groups>
   <discovery-group name="my-discovery-group">
      <jgroups-file>test-jgroups-file_ping.xml</jgroups-file>
      <jgroups-channel>activemq_broadcast_channel</jgroups-channel>
      <refresh-timeout>10000</refresh-timeout>
   </discovery-group>
</discovery-groups>

For more information on ActiveMQ Artemis clustering in general, please see the "Clusters" chapter of the user manual.