[Jboss-cvs] JBossAS SVN: r55125 - branches/Branch_4_0/tomcat/src/resources

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

Author: bstansberry at jboss.com
Date: 2006-08-03 14:46:28 -0400 (Thu, 03 Aug 2006)
New Revision: 55125

Modified:
   branches/Branch_4_0/tomcat/src/resources/tc5-cluster-service.xml
Log:
BuddyReplication disabled by default
Add ReplicationVersion comment

Modified: branches/Branch_4_0/tomcat/src/resources/tc5-cluster-service.xml
===================================================================
--- branches/Branch_4_0/tomcat/src/resources/tc5-cluster-service.xml	2006-08-03 18:36:22 UTC (rev 55124)
+++ branches/Branch_4_0/tomcat/src/resources/tc5-cluster-service.xml	2006-08-03 18:46:28 UTC (rev 55125)
@@ -20,14 +20,6 @@
         <depends>jboss:service=TransactionManager</depends>
         <!-- We need the AspectDeployer to deploy our FIELD granularity aspects -->
         <depends>jboss.aop:service=AspectDeployer</depends>
-        
-        <!-- uncomment next three statements if using JGroups multiplexer,
-               requires JGroups 2.3 or later, JBossCache 1.4.1 or later -->
-        <!--
-        <depends>jgroups.mux:name=Multiplexer</depends>
-        <attribute name="MultiplexerService">jgroups.mux:name=Multiplexer</attribute>
-        <attribute name="MultiplexerStack">fc-fast-minimalthreads</attribute>
-        -->
 
         <!-- Name of cluster. Needs to be the same for all nodes in the 
              cluster, in order to find each other
@@ -70,6 +62,32 @@
         <!--  Make sure to specify BatchModeTransactionManager only! -->
         <attribute name="TransactionManagerLookupClass">org.jboss.cache.BatchModeTransactionManagerLookup</attribute>
 
+        <!-- Configures binary format of messages sent between cluster nodes.
+             Changing this allows a later version of JBoss Cache to interoperate
+             with an earlier version. You might, for example, change this
+             if you are integrating a 4.0.4 server into a cluster with
+             servers running an earlier AS version.
+             
+             Possible values:
+             
+             1.2.3     JBC 1.2.3 or earlier; bundled with AS 4.0.3.SP1 and earlier
+             1.2.4     JBC 1.2.4
+             1.2.4.SP1 JBC 1.2.4.SP1
+             1.2.4.SP2 JBC 1.2.4.SP2; bundled with AS 4.0.4
+             
+             For version 1.3.0.GA and later, use the version name.
+        
+        	 If left blank or commented out, JBoss Cache will use the default
+        	 for that release (e.g. 1.4.0 for releases in the 1.4.0 series.
+        	 
+        	 The binary format of replication version 1.4.0 is much more efficient
+        	 than earlier releases, so there is a significant performance penalty
+        	 to trying to interoperate 1.4.0 with earlier releases vs. a pure
+        	 1.4.0 cluster.
+        
+        <attribute name="ReplicationVersion">1.4.0.GA</attribute>
+        -->
+        
 		<!-- JGroups protocol stack properties. Can also be a URL,
              e.g. file:/home/bela/default.xml
         <attribute name="ClusterProperties"></attribute>
@@ -158,10 +176,30 @@
         <!-- Max number of milliseconds to wait for a lock acquisition -->
         <attribute name="LockAcquisitionTimeout">15000</attribute>
 
-        <!-- Buddy Replication config -->
+        <!-- Buddy Replication config.
+        
+             See http://wiki.jboss.org/wiki/Wiki.jsp?page=JBossCacheBuddyReplicationDesign
+             and the JBoss Cache docs for more on buddy replication.
+             
+             By default, buddy replication is disabled.
+             
+             Following are the configuration elements likely to be changed:
+             
+             buddyReplicationEnabled  true if you want buddy replication; false if data
+                                      should be replicated to all nodes in the cluster
+                                      
+             numBuddies               to how many backup nodes should each node replicate
+                                      its state
+                                      
+             buddyPoolName            allows logical subgrouping of nodes within the cluster;
+                                      if possible, buddies will be chosen from nodes in the 
+                                      same buddy pool
+                                      
+             Do not change the data gravitation related options.             
+        -->
         <attribute name="BuddyReplicationConfig">
             <config>
-                <buddyReplicationEnabled>true</buddyReplicationEnabled>
+                <buddyReplicationEnabled>false</buddyReplicationEnabled>
                 <buddyLocatorClass>org.jboss.cache.buddyreplication.NextMemberBuddyLocator</buddyLocatorClass>
                 <buddyLocatorProperties>
                     numBuddies = 1