[jboss-cvs] JBoss Messaging SVN: r3954 - branches/Branch_JBossMessaging_1_4_0_SP3_CP/docs/userguide/en/modules.

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

Author: ataylor
Date: 2008-03-26 17:25:41 -0400 (Wed, 26 Mar 2008)
New Revision: 3954

Modified:
   branches/Branch_JBossMessaging_1_4_0_SP3_CP/docs/userguide/en/modules/configuration.xml
Log:
http://jira.jboss.org/jira/browse/JBMESSAGING-1261 - support for clustered database

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-26 21:25:05 UTC (rev 3953)
+++ branches/Branch_JBossMessaging_1_4_0_SP3_CP/docs/userguide/en/modules/configuration.xml	2008-03-26 21:25:41 UTC (rev 3954)
@@ -823,6 +823,7 @@
       <para>JBoss Messaging also ships with pre-made Persistence Manager
       configurations for MySQL, Oracle, PostgreSQL, Sybase and MS SQL Server.
       The example <filename>mysql-persistence-service.xml</filename>,
+       <filename>ndb-persistence-service.xml</filename>,
       <filename>oracle-persistence-service.xml</filename>,
       <filename>postgres-persistence-service.xml</filename> and
       <filename>sybase-persistence-service.xml</filename> and
@@ -914,6 +915,8 @@
                   
       &lt;attribute name="MaxParams"&gt;500&lt;/attribute&gt;
          
+      &lt;attribute name="UseNDBFailoverStrategy"&gt;true&lt;/attribute&gt;
+
    &lt;/mbean&gt;
 	  
 	   </programlisting>
@@ -988,6 +991,19 @@
             <para>By default the value of <literal>MaxParams</literal>
             attribute is set to <literal>100</literal></para>
          </section>
+
+       <section id="conf.persistencemanager.attributes.usendbfailoverstrategy">
+         <title>UseNDBFailoverStrategy</title>
+          <para>When running in a clustered database environment it is possible that some databases,
+             MySQL for instance, can fail during the commit of a database transaction. This can happen
+             if the database node dies whilst committing meaning that the final state of the transaction is
+             unknown. If this attribute is set to true and the above happens then the SQL statement will be
+             re-executed, however if there is a further error an assumption is made that this is because the
+             previous transaction committed successfully and the error is ignored.
+          </para>
+
+          <para>By default the value of <literal>UseNDBFailoverStrategy</literal> attribute
+          is set to <literal>false</literal></para>
       </section>
       <!-- end conf.persistencemanager.attributes -->
    </section>