This topic has not yet been written. The content below is from the topic description.
Validate Cluster Setup Before proceeding further, let’s verify that you have clustering properly configured for the two server nodes. NOTE: Each instance of the EAP is preconfigured to allocate 1.3 GB of heap space. As such, if you are starting up multiple nodes on the same server, you must be sure you have adequate memory to proceed (to avoid swapping). To reduce the memory footprint for your server instances, open the ${JBoss_HOME}/bin/run.conf file and modify the following switches assigned to the JAVA_OPTS variable: (1) Set the -Xms1304 value to something smaller (e.g., -Xms512) (2) Set the -Xmx1304 value to the same as step (1). Remember that the total memory required for your cluster will the value of your -Xmx switch times the number of servers in your cluster. To verify that you have properly set up a clustered environment, execute the following in two separate terminal windows: (For Linux/UNIX) ${JBoss_HOME}/bin/run.sh -c node1 ${JBoss_HOME}/bin/run.sh -c node2 (For Windows) ${JBoss_HOME}\bin\run.bat -c node1 ${JBoss_HOME}\bin\run.bat -c node2 NOTE: You will see a warning on both nodes, plus several errors on node2. This is due to the fact that JMS has not yet been properly configured for clustering. You can ignore these for the moment; we will address them later. To verify that your servers are clustering, note the following: On node1, you should see something similar to: On node2, you should see something similar to (before the JMS errors): Note that both outputs identify a total of two members in the cluster. Each member identifies itself via a host IP and multicast port (e.g., I am (127.0.0.1:55300)), plus gives details on all members of the cluster (e.g., All Members : 2 (127.0.0.1:55300, 127.0.0.1:55400)). Now that you have verified your servers are clustering, use Control-C to stop both servers. The next step is creating your JMS cluster is to update the appropriate JMS-centric settings.