[jboss-cvs] JBossAS SVN: r83583 - projects/docs/enterprise/4.3.4/Server_Configuration_Guide/en-US.

[jboss-cvs-commits at lists.jboss.org]

Author: irooskov at redhat.com
Date: 2009-01-28 18:41:06 -0500 (Wed, 28 Jan 2009)
New Revision: 83583

Modified:
   projects/docs/enterprise/4.3.4/Server_Configuration_Guide/en-US/Clustering_Guide_JBoss_Cache_JGroups.xml
Log:
updated guide with JBPAPP-1649 fix from Jimmy


Modified: projects/docs/enterprise/4.3.4/Server_Configuration_Guide/en-US/Clustering_Guide_JBoss_Cache_JGroups.xml
===================================================================
--- projects/docs/enterprise/4.3.4/Server_Configuration_Guide/en-US/Clustering_Guide_JBoss_Cache_JGroups.xml	2009-01-28 22:54:46 UTC (rev 83582)
+++ projects/docs/enterprise/4.3.4/Server_Configuration_Guide/en-US/Clustering_Guide_JBoss_Cache_JGroups.xml	2009-01-28 23:41:06 UTC (rev 83583)
@@ -1158,8 +1158,16 @@
 		     Unfortunately, setting the multicast ports is not so simple. As described above, by default there are four separate JGroups channels in the standard JBoss AS all configuration, and each should be given a unique port. There are no command line switches to set these, but the standard configuration files do use system properties to set them.  So, they can be configured from the command line by using -D. For example,
 	     </para>
 <programlisting>
-	/run.sh -u 230.1.2.3 -g QAPartition -Djboss.hapartition.mcast_port=12345 -Djboss.webpartition.mcast_port=23456 -Djboss.ejb3entitypartition.mcast_port=34567 -Djboss.ejb3sfsbpartition.mcast_port=45678 -b 192.168.1.100 -c all
+	/run.sh -u 230.1.2.3 -g QAPartition
+	-Djboss.messaging.controlchanneludpport_port=21234
+	-Djboss.messaging.datachanneludpport_port=22345
+	-Djboss.hapartition.mcast_port=12345 -Djboss.webpartition.mcast_port=23456 -Djboss.ejb3entitypartition.mcast_port=34567 -Djboss.ejb3sfsbpartition.mcast_port=45678 -b 192.168.1.100 -c all
 </programlisting>
+<note>
+	<para>
+		The ports in the above example are randomly chosen for demonstration purposes only.
+	</para>
+</note>
 	
 <para><emphasis>Why isn't it sufficient to change the group name?</emphasis></para>
 <para>
@@ -1168,7 +1176,7 @@
 			     
 	<para><emphasis>Why do I need to change the multicast port if I change the address?</emphasis></para>
 		<para>
-			It should be sufficient to just change the address, but there is a problem on several operating systems whereby packets addressed to a particular multicast port are delivered to all listeners on that port, regardless of the multicast address they are listening on. So the recommendation is to change both the address and the port.
+			It should be sufficient to just change the address, but there is a problem on several operating systems whereby packets addressed to a particular multicast port are delivered to all listeners on that port, regardless of the multicast address they are listening on.  This problem has been fixed for Linux, where it was most prevalent, as of 4.2 CP06 and 4.3 CP04, but if you have problems when just changing the address, you should change the ports as well.
 		</para>
 </section>