[jboss-cvs] JBoss Messaging SVN: r3928 - in branches/Branch_JBossMessaging_1_4_0_SP3_CP: tests/src/org/jboss/test/messaging/core and 1 other directory.

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

Author: timfox
Date: 2008-03-25 11:43:16 -0400 (Tue, 25 Mar 2008)
New Revision: 3928

Modified:
   branches/Branch_JBossMessaging_1_4_0_SP3_CP/docs/userguide/en/modules/c_configuration.xml
   branches/Branch_JBossMessaging_1_4_0_SP3_CP/docs/userguide/en/modules/configuration.xml
   branches/Branch_JBossMessaging_1_4_0_SP3_CP/tests/src/org/jboss/test/messaging/core/PostOfficeTestBase.java
Log:
http://jira.jboss.org/jira/browse/JBMESSAGING-1230


Modified: branches/Branch_JBossMessaging_1_4_0_SP3_CP/docs/userguide/en/modules/c_configuration.xml
===================================================================
--- branches/Branch_JBossMessaging_1_4_0_SP3_CP/docs/userguide/en/modules/c_configuration.xml	2008-03-25 14:52:43 UTC (rev 3927)
+++ branches/Branch_JBossMessaging_1_4_0_SP3_CP/docs/userguide/en/modules/c_configuration.xml	2008-03-25 15:43:16 UTC (rev 3928)
@@ -78,6 +78,7 @@
 		   	duplicate messages, and discarding them if they arrive. Duplicate checking
 		   	is a very powerful technique that can remove the need for XA transactions
 		   	in many cases.</para>
+		<para>In the clustered case. JBM is by default configured to detect duplicate automatically messages by default</para>
 	      </section>
       
       

Modified: branches/Branch_JBossMessaging_1_4_0_SP3_CP/docs/userguide/en/modules/configuration.xml
===================================================================
--- branches/Branch_JBossMessaging_1_4_0_SP3_CP/docs/userguide/en/modules/configuration.xml	2008-03-25 14:52:43 UTC (rev 3927)
+++ branches/Branch_JBossMessaging_1_4_0_SP3_CP/docs/userguide/en/modules/configuration.xml	2008-03-25 15:43:16 UTC (rev 3928)
@@ -563,6 +563,11 @@
                   
       &lt;attribute name="CastTimeout"&gt;50000&lt;/attribute&gt;
       
+      &lt;!-- Set this to true if you want failover of connections to occur when a node is shut down --&gt;
+      
+      &lt;attribute name="FailoverOnNodeLeave"&gt;false&lt;/attribute&gt;
+            
+      
       &lt;!-- JGroups stack configuration for the data channel - used for sending data across the cluster --&gt; 
                    
       &lt;!-- By default we use the TCP stack for data --&gt;                  
@@ -741,6 +746,12 @@
             <para>The default value is <literal>5000</literal>
             milliseconds.</para>
          </section>
+	 <section id="conf.postoffice.attributes.failoveronnodeleave">
+            <title>FailoverOnNodeLeave</title>		 
+	    <para>If this attribute is <literal>true</literal> then if a server node is shut down cleanly, then this will cause any
+			 connections on the shutting down node to failover onto another node.</para>		 
+	     <para>The default value for this is attribute is <literal>false</literal></para>				 
+         </section>  	 
          <section id="conf.postoffice.attributes.maxconcurrentreplications">
             <title>MaxConcurrentReplications</title>
             <para>The maximum number of concurrent replication requests to

Modified: branches/Branch_JBossMessaging_1_4_0_SP3_CP/tests/src/org/jboss/test/messaging/core/PostOfficeTestBase.java
===================================================================
--- branches/Branch_JBossMessaging_1_4_0_SP3_CP/tests/src/org/jboss/test/messaging/core/PostOfficeTestBase.java	2008-03-25 14:52:43 UTC (rev 3927)
+++ branches/Branch_JBossMessaging_1_4_0_SP3_CP/tests/src/org/jboss/test/messaging/core/PostOfficeTestBase.java	2008-03-25 15:43:16 UTC (rev 3928)
@@ -96,7 +96,7 @@
                                  sc.getPostOfficeSQLProperties(), true, nodeID,
                                  "Clustered", ms, pm, tr, ff, cf, idm, cn,
                                  groupName, jChannelFactory,
-                                 stateTimeout, castTimeout, true, 100);
+                                 stateTimeout, castTimeout, true, 100, false);
 
       postOffice.start();