28.6.2.2. Isolating Channels for Different Services on the Same Set of JBoss Enterprise Application Platform Instances

This section addresses the usual case: a cluster of three machines, each of which has, for example, an HAPartition deployed alongside JBoss Cache for web session clustering. The HAPartition channels should not communicate with the JBoss Cache channels. Ensuring proper isolation of these channels is straightforward, and is usually handled by the application server without any alterations on the part of the user.

To isolate channels for different services from each other on the same set of application server instances, each channel must have its own group name. The configurations that ship with JBoss Enterprise Application Platform ensure that this is the case. However, if you create a custom service that uses JGroups directly, you must use a unique group name. If you create a custom JBoss Cache configuration, ensure that you provide a unique value in the clusterName configuration property.

In releases prior to JBoss Enterprise Application Platform 5, different channels running in the same application server also had to use unique multicast ports. With the JGroups shared transport introduced in JBoss Enterprise Application Platform 5 (see Section 21.1.2, “The JGroups Shared Transport”), it is now common for multiple channels to use the same transport protocol and its sockets. This makes configuration easier, which is one of the main benefits of the shared transport. However, if you decide to create your own custom JGroups protocol stack configuration, be sure to configure its transport protocols with a multicast port that is different from the ports used in other protocol stacks.

./run.sh -g QAPartition -b 192.168.1.100 -c production

./run.sh -g QAPartition -b 192.168.1.100 -c production

<property name="clusterName">${jboss.partition.name:DefaultPartition}-SFSBCache</property>

<property name="clusterName">${jboss.partition.name:DefaultPartition}-SFSBCache</property>