TechNote (Archived)

ColdFusion MX 7 clustering configures without errors but doesn’t work

Issue

---

When running ColdFusion MX 7 in the multiserver configuration, the Enterprise Manager can create connector-based clusters. However, if MultiCasting is not enabled on your network, the cluster will not work. The symptom is that only one of the ColdFusion MX servers in the cluster will serve the page requests, and if the working server is shut down, the requests will not failover to other servers in the cluster.

Reason

---

If MultiCasting is not enabled on the network, the servers never actually join the cluster, therefore, at runtime there is no cluster. When a server joins a cluster, you will see the following entries in the server log filejrun_root\logs\{server_name}-event.log.

 08/09 16:52:17 info Clusterable service ServletUsersService discovered ClusterManager on 10.1.244.115:4160, cluster domain: newCluster (Lookup Service's JINI-ID: 924c1ad1-827c-45fe-b98e-970df7bc7ce7)  08/09 16:52:17 info ServletUsersService successfully joined a JNDI lookup service (assigned JINI-ID 0ca3b1e3-1de0-43c2-8326-bb8ec855b5b6)  08/09 16:52:17 info Clusterable service ReplicationIdService discovered ClusterManager on 10.1.244.115:4160, cluster domain: newCluster (Lookup Service's JINI-ID: 924c1ad1-827c-45fe-b98e-970df7bc7ce7) 

Solution

---

If you have configured a ColdFusion MX cluster and it is not working properly, you can manually configure the cluster to include the IP addresses of all the member servers so that it will work even if the network doesn't have MultiCasting enabled.

1. Edit thejrun_root\servers\{server_name}\SERVER-INF\jrun.xml file.
2. Add the unicastPeer attribute after theClusterDeployerService tag block.
3. Set the attribute to include the IP addresses of all the member servers in the cluster (separate each entry using a space delimiter).
   
   For example:

    <service outputclass="jrunx.cluster.ClusterDeployerService" name="ClusterDeployerService"><attribute name="deployDirectory">{jrun.server.rootdir}/SERVER-INF/cluster</attribute><attribute name="deactivated">false</attribute></service><attribute name="unicastPeer">192.168.2.10 192.168.2.20 192.168.2.33</attribute></service> 

4. Make this change to the jrun.xml file for each server in the cluster. If you prefer, you can do the same thing using the JRun Management Console (make sure all the servers in the cluster are running at the time).
5. Reboot all servers in the cluster after making the change.

Search Support

---