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

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

Author: gaohoward
Date: 2010-01-04 04:51:19 -0500 (Mon, 04 Jan 2010)
New Revision: 7929

Modified:
   branches/Branch_1_4/docs/userguide/en/modules/ordering_group.xml
Log:
JBMESSAGING-1779


Modified: branches/Branch_1_4/docs/userguide/en/modules/ordering_group.xml
===================================================================
--- branches/Branch_1_4/docs/userguide/en/modules/ordering_group.xml	2009-12-28 08:38:32 UTC (rev 7928)
+++ branches/Branch_1_4/docs/userguide/en/modules/ordering_group.xml	2010-01-04 09:51:19 UTC (rev 7929)
@@ -15,14 +15,14 @@
 
   <itemizedlist>
     <listitem>For CLIENT_ACKNOWLEDGE mode, the Message.acknowledge() method signals the completion state.</listitem>
-    <listitem>For AUTO_ACKNOWLEDGE and DUPS_OK_ACKNOWLEDGE modes, the completion of the message is identified by either
+    <listitem>For AUTO_ACKNOWLEDGE mode, the completion of the message is identified by either
 
       <para>1) successful returning from the MessageConsumer.receive() methods, or</para>
       <para>2) successful returning from the onMessage() call of the MessageListener();</para>
     </listitem>
+    <listitem>Ordering Group cannot work with DUPS_OK_ACKNOWLEDGE mode unless the batch acknowlegement size is limited to 1 (DupsOKBatchSize).</listitem>
   </itemizedlist>
-    
-    
+
   <para>If the message consumer is closed, the current message processing is deemed to be finished, even if the acknowledge is not called before consumer close.</para>
 
   <para>Rule 2. In case of transactional receiving, the next message will not be delivered until the transaction that includes the receiving of the previous message has been committed. If the transaction is rolled back, the previous message will be cancelled back to the JMS server and thus available for the next delivery.