You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tomcat.apache.org by ma...@apache.org on 2010/07/21 12:59:31 UTC
svn commit: r966178 - /tomcat/trunk/webapps/docs/config/cluster-manager.xml
Author: markt
Date: Wed Jul 21 10:59:31 2010
New Revision: 966178
URL: http://svn.apache.org/viewvc?rev=966178&view=rev
Log:
Correct explanation. mapSendOptions=6 is synchronous, not asynchronous.
Modified:
tomcat/trunk/webapps/docs/config/cluster-manager.xml
Modified: tomcat/trunk/webapps/docs/config/cluster-manager.xml
URL: http://svn.apache.org/viewvc/tomcat/trunk/webapps/docs/config/cluster-manager.xml?rev=966178&r1=966177&r2=966178&view=diff
==============================================================================
--- tomcat/trunk/webapps/docs/config/cluster-manager.xml (original)
+++ tomcat/trunk/webapps/docs/config/cluster-manager.xml Wed Jul 21 10:59:31 2010
@@ -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.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org