Author: markt
Date: Tue Apr 28 14:55:13 2015
New Revision: 1676552
URL: http://svn.apache.org/r1676552
Log:
Fix https://bz.apache.org/bugzilla/show_bug.cgi?id=57864
Make it clearer that hex values are not valid for cluster send options
Based on a patch by Kyohei Nakamura
Modified:
tomcat/trunk/webapps/docs/config/cluster.xml
Modified: tomcat/trunk/webapps/docs/config/cluster.xml
URL:
http://svn.apache.org/viewvc/tomcat/trunk/webapps/docs/config/cluster.xml?rev=1676552&r1=1676551&r2=1676552&view=diff
==============================================================================
--- tomcat/trunk/webapps/docs/config/cluster.xml (original)
+++ tomcat/trunk/webapps/docs/config/cluster.xml Tue Apr 28 14:55:13 2015
@@ -123,11 +123,11 @@
<code>Channel.SEND_OPTIONS_SYNCHRONIZED_ACK = 0x0004</code><br/>
<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/>
+ So to use ACK and ASYNC messaging, the flag would be <code>10</code>
(8+2)
+ <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>
+ to the order in which they were sent.</p>
</attribute>
<attribute name="channelStartOptions" required="false">
<p>Sets the start and stop flags for the <Channel> object used by
the cluster.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org
