From: markt <markt@13f79535-47bb-0310-9956-ffa450edef68>
Date: Wed, 21 Jul 2010 10:59:31 +0000 (+0000)
Subject: Correct explanation. mapSendOptions=6 is synchronous, not asynchronous.
X-Git-Url: https://git.internetallee.de/?a=commitdiff_plain;h=c6ebcd443baba29cb3050d9773ed42e1cdcc00d0;p=tomcat7.0

Correct explanation. mapSendOptions=6 is synchronous, not asynchronous.

git-svn-id: https://svn.apache.org/repos/asf/tomcat/trunk@966178 13f79535-47bb-0310-9956-ffa450edef68
---

diff --git a/webapps/docs/config/cluster-manager.xml b/webapps/docs/config/cluster-manager.xml
index 6813829cb..7c5119a31 100644
--- a/webapps/docs/config/cluster-manager.xml
+++ b/webapps/docs/config/cluster-manager.xml
@@ -112,7 +112,7 @@
      <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).<br/>
+       messages, the default value is <code>6</code>(synchronous).<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.