Issue
Network Error while Registering a Remote Instance for a Cluster
Solution
Please go through the following steps to manually configure a Cluster and Register the remote instance:
1. Create the Coldfusion instances as needed. Make sure to check Windows Service option when creating the instance. Open administrator for each of the instances and enable J2EE Session Variables located under Settings -> Memory Variables.
2. Go to the path C:/JRun4/servers/{INSTANCE_NAME}/SERVER-INF. Open the jrun.xml file and search for "ClusterManager" which will be as mentioned below.
<service class="jrunx.cluster.ClusterManager" name="ClusterManager">
<attribute name="bindToJNDI">true</attribute>
<attribute name="enabled">false</attribute>
<attribute name="clusterDomain">default</attribute>
<!-- While we will discover nearby peers automatically without prior knowledge -->
<!-- of them, you can also add as many specific hosts as you wish; these unicast -->
<!-- peers do not need to be nearby or reachable via multicast. -->
<!--EXAMPLE: <attribute name="unicastPeer">sneville</attribute> -->
<service class="jrunx.cluster.ClusterDeployerService" name="ClusterDeployerService">
<attribute name="deployDirectory">{jrun.server.rootdir}/SERVER-INF/cluster</attribute>
<attribute name="deactivated">true</attribute>
</service>
Change the settings colored "Bolded" as below
<service class="jrunx.cluster.ClusterManager" name="ClusterManager">
<attribute name="bindToJNDI">true</attribute>
<attribute name="enabled">true</attribute>
<attribute name="clusterDomain"><Mention the name of cluster></attribute>
<!-- While we will discover nearby peers automatically without prior knowledge -->
<!-- of them, you can also add as many specific hosts as you wish; these unicast -->
<!-- peers do not need to be nearby or reachable via multicast. -->
<!--EXAMPLE: <attribute name="unicastPeer">sneville</attribute> -->
<service class="jrunx.cluster.ClusterDeployerService" name="ClusterDeployerService">
<attribute name="deployDirectory">{jrun.server.rootdir}/SERVER-INF/cluster</attribute>
<attribute name="deactivated">true</attribute>
</service>
3. Search for ProxyService in jrun.xml. Under ProxyService, look for deactivated property and change the value to false
4. To test the cluster configuration:-
a) Open the command prompt and go to C:/JRun4/bin. Run the following command
jrun –start <INSTANCE_NAME>
b) Repeat the same steps on another machine and start another instance.
c) To confirm that the clustering is functioning properly, check if the first instance recognizes the second instance or not.
5. Configure the connector using the webserver configuration tool.
6. Test the sessiontest.cfm page to confirm that the clustering is functioning properly.
7. To Enable the session replication for the servers, Add the following tags to jrun-web.xml located at:
c:/jrun4/servers/{INSTANCE_NAME}/cfusion-ear/cfusion-war/WEB-INF directory after <jrun-web-app>.
If the jrun-web.xml is not present in the directory, copy it from c:/jrun4/servers/cfusion/cfusion-ear/cfusion-war/WEB-INF and make the change.
<session-config>
<replication-config>
<active>true</active>
<buddy-name>*</buddy-name>
</replication-config>
<persistence-config>
<active>false</active>
</persistence-config>
</session-config>
8. Stop the coldfusion instances from the command prompt. Start them from the services panel. Restart IIS.
9. Test your sessiontest.cfm to make sure sessions are replicated.
Additional information
1. The cluster name must be unique over the network which is specified in the clusterdomain.
2. If the services for ColdFusion instances are not created while creating the instances. Run the steps mentioned below:-
jrunsvc -install InstanceName
