[jboss-cvs] JBossAS SVN: r102387 - projects/docs/enterprise/5.0.1/Administration_And_Configuration_Guide/en-US.

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

Author: laubai
Date: 2010-03-14 21:47:33 -0400 (Sun, 14 Mar 2010)
New Revision: 102387

Modified:
   projects/docs/enterprise/5.0.1/Administration_And_Configuration_Guide/en-US/Clustering_Guide_JGroups.xml
Log:
Corrected Clustering JGroups chapter as per JBPAPP-2648.

Modified: projects/docs/enterprise/5.0.1/Administration_And_Configuration_Guide/en-US/Clustering_Guide_JGroups.xml
===================================================================
--- projects/docs/enterprise/5.0.1/Administration_And_Configuration_Guide/en-US/Clustering_Guide_JGroups.xml	2010-03-15 01:21:38 UTC (rev 102386)
+++ projects/docs/enterprise/5.0.1/Administration_And_Configuration_Guide/en-US/Clustering_Guide_JGroups.xml	2010-03-15 01:47:33 UTC (rev 102387)
@@ -745,7 +745,7 @@
 <section id="jgroups-fd-fd">
           <title>FD</title>
 	  <para>
-		  <literal>FD</literal> is a failure detection protocol based on 'heartbeat' messages. This protocol requires that eat node periodically ping its neighbour. If the neighbour fails to respond, the calling node sends a <literal>SUSPECT</literal> message to the cluster. The current group coordinator can optionally verify that the suspected node is dead (<literal>VERIFY_SUSPECT</literal>). If the node is still considered dead after this verification step, the coordinator updates the cluster's membership view. The following is an example of <literal>FD</literal> configuration:
+		  <literal>FD</literal> is a failure detection protocol based on 'heartbeat' messages. This protocol requires that each node periodically ping its neighbour. If the neighbour fails to respond, the calling node sends a <literal>SUSPECT</literal> message to the cluster. The current group coordinator can optionally verify that the suspected node is dead (<literal>VERIFY_SUSPECT</literal>). If the node is still considered dead after this verification step, the coordinator updates the cluster's membership view. The following is an example of <literal>FD</literal> configuration:
 	  </para>
 
 <programlisting>
@@ -766,7 +766,7 @@
 		      are-you-alive messages from a node before the node is suspected. The default is 2.</para>
             </listitem>
             <listitem>
-              <para><emphasis role="bold">shun</emphasis> specifies whether a failed node will be forbidden from sending messages to the group without formally rejoining. A shunned node would need to rejoin the cluster via the discovery process. JGroups allows applications to configure a channel such that, when a channel is shunned, the process of rejoining the cluster and transferring state. (This is default behavior for JBoss Application Server.)</para>
+              <para><emphasis role="bold">shun</emphasis> specifies whether a failed node will be forbidden from sending messages to the group without formally rejoining. A shunned node would need to rejoin the cluster via the discovery process. JGroups allows applications to configure a channel such that, when a channel is shunned, the process of rejoining the cluster and transferring state takes place automatically. (This is default behavior for JBoss Application Server.)</para>
             </listitem>
           </itemizedlist>
           <note>
@@ -866,19 +866,10 @@
 		</para>
 	</listitem>
 	<listitem>
-						<para>
-			Members will only be suspected when TCP connection breaks
+		<para>
+			Members will only be suspected when TCP connection breaks, so hung members will not be detected.
 		</para>
 	</listitem>
-</itemizedlist>
-
-
-	<itemizedlist>
-		<listitem>
-			<para>
-			So hung members will not be detected.
-		</para>
-	</listitem>
 	<listitem>
 		<para>