From b9576f492ae081181275ba5e589f01050fa526f0 Mon Sep 17 00:00:00 2001
From: markt <markt@13f79535-47bb-0310-9956-ffa450edef68>
Date: Wed, 21 Jul 2010 10:58:56 +0000
Subject: [PATCH] Add note about message processing order.

git-svn-id: https://svn.apache.org/repos/asf/tomcat/trunk@966177 13f79535-47bb-0310-9956-ffa450edef68
---
 webapps/docs/config/cluster-manager.xml | 8 ++++++--
 webapps/docs/config/cluster.xml         | 3 +++
 2 files changed, 9 insertions(+), 2 deletions(-)

diff --git a/webapps/docs/config/cluster-manager.xml b/webapps/docs/config/cluster-manager.xml
index 2f19f06d2..6813829cb 100644
--- a/webapps/docs/config/cluster-manager.xml
+++ b/webapps/docs/config/cluster-manager.xml
@@ -110,8 +110,12 @@
   <subsection name="org.apache.catalina.ha.session.BackupManager Attributes">
     <attributes>
      <attribute name="mapSendOptions" required="false">
-       The backup manager uses a replicated map, this map is sending and receiving messages.
-       You can setup the flag for how this map is sending messages, the default value is <code>6</code>(asynchronous).
+       The backup manager uses a replicated map, this map is sending and
+       receiving messages. You can setup the flag for how this map is sending
+       messages, the default value is <code>6</code>(asynchronous).<br/>
+       Note that if you use asynchronous messaging it is possible for update
+       messages for a session to be processed by the receiving node in a
+       different order to the order in which they were sent.
      </attribute>
     </attributes>
   </subsection>
diff --git a/webapps/docs/config/cluster.xml b/webapps/docs/config/cluster.xml
index 2626bff4a..a88ea93ec 100644
--- a/webapps/docs/config/cluster.xml
+++ b/webapps/docs/config/cluster.xml
@@ -125,6 +125,9 @@
       <code>Channel.SEND_OPTIONS_ASYNCHRONOUS = 0x0008</code><br/>
       <code>Channel.SEND_OPTIONS_USE_ACK = 0x0002</code><br/>
       So to use ACK and ASYNC messaging, the flag would be <code>10 (8+2) or 0x000B</code><br/>
+      Note that if you use ASYNC messaging it is possible for update messages
+      for a session to be processed by the receiving nodes in a different order
+      to the order in which they were sent.
       </p>
     </attribute>
     <attribute name="channelStartOptions" required="false">
-- 
2.11.0