The chapter should contain at least: - configuration of broadcast group, discovery group and cluster connections - server-side load balancing - working with jgroups
Here's link to upstream documentation on HornetQ clustering: http://docs.jboss.org/hornetq/2.3.0.Final/docs/user-manual/html/clusters.html
Hi Nidhi, there is one more issue in configuration of clustering using JGroups. For broadcast group there should be: <broadcast-groups> <broadcast-group name="bg-group1"> <jgroups-stack>udp</jgroups-stack> <jgroups-channel>udp</jgroups-channel> <broadcast-period>2000</broadcast-period> <connector-ref> netty </connector-ref> </broadcast-group> </broadcast-groups> and for discovery group: <discovery-groups> <discovery-group name="dg-group1"> <jgroups-stack>udp</jgroups-stack> <jgroups-channel>udp</jgroups-channel> <refresh-timeout>10000</refresh-timeout> </discovery-group> </discovery-groups> Attribute jgroups-stack - The name of a stack defined in the org.jboss.as.clustering.jgroups subsystem. Attribute jgroups-file cannot be set in EAP 6 and all occurrences (paragraphs) must be removed. For HornetQ in EAP we don't support chain cluster topology. I'd like to remove it from doc from chapter - 19.5.1. About Server Side Load Balancing: Chain cluster: In a chain cluster, each node in the cluster is not connected to every node in the cluster directly. Here the nodes form a chain with a node on each end of the chain and all other nodes only connect to the previous and next nodes in the chain. To create a chain cluster, node A would define a cluster connection that connects to node B, and node B would define a cluster connection that connects to node C. The messages will move from node A>B>C in this case. The attribute max-hops is set to 2. Thanks, Mirek
Thanks Nidhi
*** Bug 970409 has been marked as a duplicate of this bug. ***
*** Bug 1012469 has been marked as a duplicate of this bug. ***
*** Bug 1029494 has been marked as a duplicate of this bug. ***