[jboss-cvs] JBossAS SVN: r100857 - projects/docs/enterprise/5.0/mod_cluster/en-US.
jboss-cvs-commits at lists.jboss.org
jboss-cvs-commits at lists.jboss.org
Thu Feb 11 02:27:14 EST 2010
Author: gmeintjes
Date: 2010-02-11 02:27:14 -0500 (Thu, 11 Feb 2010)
New Revision: 100857
Modified:
projects/docs/enterprise/5.0/mod_cluster/en-US/Book_Info.xml
projects/docs/enterprise/5.0/mod_cluster/en-US/ConfigurationForJBossAS.xml
projects/docs/enterprise/5.0/mod_cluster/en-US/MigratingFromModJK.xml
projects/docs/enterprise/5.0/mod_cluster/en-US/QuickStartGuide.xml
projects/docs/enterprise/5.0/mod_cluster/en-US/Revision_History.xml
Log:
amend as per JBPAPP-3273
Modified: projects/docs/enterprise/5.0/mod_cluster/en-US/Book_Info.xml
===================================================================
--- projects/docs/enterprise/5.0/mod_cluster/en-US/Book_Info.xml 2010-02-11 06:29:41 UTC (rev 100856)
+++ projects/docs/enterprise/5.0/mod_cluster/en-US/Book_Info.xml 2010-02-11 07:27:14 UTC (rev 100857)
@@ -7,7 +7,7 @@
<productname>JBoss Enterprise Application Platform</productname>
<productnumber>5.0</productnumber>
<edition>1</edition>
- <pubsnumber>1.9</pubsnumber>
+ <pubsnumber>2.0</pubsnumber>
<abstract>
<para>
mod_cluster is an httpd-based load balancer that uses a
Modified: projects/docs/enterprise/5.0/mod_cluster/en-US/ConfigurationForJBossAS.xml
===================================================================
--- projects/docs/enterprise/5.0/mod_cluster/en-US/ConfigurationForJBossAS.xml 2010-02-11 06:29:41 UTC (rev 100856)
+++ projects/docs/enterprise/5.0/mod_cluster/en-US/ConfigurationForJBossAS.xml 2010-02-11 07:27:14 UTC (rev 100857)
@@ -3,11 +3,11 @@
]>
<chapter id="chap-mod_cluster-Configuring_for_JBoss_AS">
<title>Configuring for JBoss AS</title>
- <note>
+<!-- <note>
<para>
mod_cluster currently works with <application>JBoss AS 5.0</application>.
</para>
- </note>
+ </note> -->
<section id="sect-mod_cluster-Configuring_for_JBoss_AS-Common_Configuration">
<title>Common Configuration</title>
<para>
@@ -15,7 +15,7 @@
</para>
<programlisting>
-<filename>$JBOSS_HOME/server/<replaceable>$PROFILE/deploy</replaceable>/jbossweb.sar/server.xml</filename>
+<filename>$JBOSS_HOME/server/$PROFILE/deploy/jbossweb.sar/server.xml</filename>
</programlisting>
<formalpara id="form-mod_cluster-Common_Configuration-Add_a_lifecycle_listener.">
<title>Add a lifecycle listener.</title>
@@ -24,9 +24,9 @@
</para>
</formalpara>
<formalpara id="form-mod_cluster-Common_Configuration-Define_a_jvmRoute_for_each_server.">
- <title>Define a <parameter>jvmRoute</parameter> for each server.</title>
+ <title>Define a jvmRoute for each server.</title>
<para>
- mod_cluster requires the Catalina engine of each node to define a unique <parameter>jvmRoute</parameter> attribute. The <parameter>jvmRoute</parameter> uniquely identifies the engine instance in httpd.
+ mod_cluster requires the Catalina engine of each node to define a unique jvmRoute attribute. The jvmRoute uniquely identifies the engine instance in httpd.
</para>
</formalpara>
<formalpara id="form-mod_cluster-Common_Configuration-Adjust_load_balance_factor_calculation_period.">
@@ -413,7 +413,7 @@
<property>stickySession</property>
</entry>
<entry>
-<literal>true</literal>
+true
</entry>
<entry>
Indicates whether subsequent requests for a given session should be routed to the same node, if possible.
@@ -427,7 +427,8 @@
false
</entry>
<entry>
-Indicates whether the httpd proxy should remove session stickiness in the event that the balancer is unable to route a request to the node to which it is stuck. This property is ignored if <property>stickySession</property> is false.
+Indicates whether the httpd proxy should remove session ID from headers and parameters in the event that the balancer is unable to route a request to the node to which it is stuck. This property is ignored if <property>stickySession</property> is false.
+
</entry>
</row>
<row>
Modified: projects/docs/enterprise/5.0/mod_cluster/en-US/MigratingFromModJK.xml
===================================================================
--- projects/docs/enterprise/5.0/mod_cluster/en-US/MigratingFromModJK.xml 2010-02-11 06:29:41 UTC (rev 100856)
+++ projects/docs/enterprise/5.0/mod_cluster/en-US/MigratingFromModJK.xml 2010-02-11 07:27:14 UTC (rev 100857)
@@ -2,7 +2,7 @@
<!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
]>
<chapter id="chap-mod_cluster-Migration_from_mod_jk">
- <title>Migration from mod_jk</title>
+ <title>Migration</title>
<section id="sect-mod_cluster-Migration_from_mod_jk-Migration_from_mod_jk_to_mod_cluster">
<title>Migration from mod_jk to mod_cluster</title>
<para>
@@ -314,5 +314,334 @@
</table>
</section>
+ <section>
+ <title>Migration from mod_proxy</title>
+ <para>
+ To migrate from mod_proxy to mod_cluster, refer to http://www.jboss.org/mod_cluster/native/mod_proxy.html.
+ </para>
+
+<!-- <para>
+ As mod_cluster is a sophisticated balancer migration from mod_proxy to mod_cluster is strait forward. mod_cluster replaces a reverse proxy with loadbalancing. A reversed proxy is configured like:
+ </para>
+<programlisting><![CDATA[
+ProxyRequests Off
+
+<Proxy *>
+Order deny,allow
+Allow from all
+</Proxy>
+
+ProxyPass /foo http://foo.example.com/bar
+ProxyPassReverse /foo http://foo.example.com/bar
+]]></programlisting>
+ <para>
+ All the general proxy parameters could be used in mod_cluster they work like in mod_proxy, only the balancers and the workers definitions are slightly different.
+ </para>
+ <para>
+ Workers:
+ </para>
+ <table>
+ <title>Worker Property Transfer</title>
+ <tgroup align="left" cols="3" colsep="1" rowsep="1">
+ <colspec colname="c1"></colspec>
+ <colspec colname="c2"></colspec>
+ <colspec colname="c3"></colspec>
+ <thead>
+ <row>
+ <entry>
+ mod_jk worker property
+ </entry>
+ <entry>
+ <classname>mod_cluster configuration</classname> Parameter
+ </entry>
+ <entry>
+ Remarks
+ </entry>
+ </row>
+ </thead>
+ <tbody>
+ <row>
+ <entry>
+ host
+ </entry>
+ <entry>
+ -
+ </entry>
+ <entry>
+ It is read from the <Connector/> Address information
+ </entry>
+ </row>
+ <row>
+ <entry>
+ port
+ </entry>
+ <entry>
+ -
+ </entry>
+ <entry>
+ It is read from the <Connector/> Port information
+ </entry>
+ </row>
+ <row>
+ <entry>
+ type
+ </entry>
+ <entry>
+ -
+ </entry>
+ <entry>
+ It is read from the <Connector/> Protocol information
+ </entry>
+ </row>
+ <row>
+ <entry>
+ route
+ </entry>
+ <entry>
+ -
+ </entry>
+ <entry>
+ It is read from the <Engine/> JVMRoute information
+ </entry>
+ </row>
+ <row>
+ <entry>
+ domain
+ </entry>
+ <entry>
+ domain
+ </entry>
+ <entry>
+ Not supported in this version
+ </entry>
+ </row>
+ <row>
+ <entry>
+ redirect
+ </entry>
+ <entry>
+ -
+ </entry>
+ <entry>
+ The nodes with <literal>loadfactor = 0</literal> are standby nodes that will be used when there are no other nodes available
+ </entry>
+ </row>
+ <row>
+ <entry>
+ socket_timeout
+ </entry>
+ <entry>
+ nodeTimeout
+ </entry>
+ <entry>
+ Default: 10 seconds
+ </entry>
+ </row>
+ <row>
+ <entry>
+ socket_keepalive
+ </entry>
+ <entry>
+ -
+ </entry>
+ <entry>
+ <classname>KEEP_ALIVE</classname> os is always on in mod_cluster
+ </entry>
+ </row>
+ <row>
+ <entry>
+ connection_pool_size
+ </entry>
+ <entry>
+ -
+ </entry>
+ <entry>
+ The max size is calculated to be <literal>AP_MPMQ_MAX_THREADS+1</literal> (max)
+ </entry>
+ </row>
+ <row>
+ <entry>
+ connection_pool_minsize
+ </entry>
+ <entry>
+ smax
+ </entry>
+ <entry>
+ The default is max
+ </entry>
+ </row>
+ <row>
+ <entry>
+ connection_pool_timeout
+ </entry>
+ <entry>
+ ttl
+ </entry>
+ <entry>
+ Time-to-live when over smax connections. Default: 60 seconds
+ </entry>
+ </row>
+ <row>
+ <entry>
+ -
+ </entry>
+ <entry>
+ workerTimeout
+ </entry>
+ <entry>
+ Max time to wait for a free worker. Default: 1 second
+ </entry>
+ </row>
+ <row>
+ <entry>
+ retries
+ </entry>
+ <entry>
+ maxAttempts
+ </entry>
+ <entry>
+ Max retries before returning an error. Default: 3
+ </entry>
+ </row>
+ <row>
+ <entry>
+ recovery_options
+ </entry>
+ <entry>
+ -
+ </entry>
+ <entry>
+ mod_cluster behaves like mod_jk with value <varname>7</varname>
+ </entry>
+ </row>
+ <row>
+ <entry>
+ fail_on_status
+ </entry>
+ <entry>
+ -
+ </entry>
+ <entry>
+ Not supported
+ </entry>
+ </row>
+ <row>
+ <entry>
+ max_packet_size
+ </entry>
+ <entry>
+ iobuffersize/receivebuffersize
+ </entry>
+ <entry>
+ Not supported in this version. Use <varname>ProxyIOBufferSize</varname>
+ </entry>
+ </row>
+ <row>
+ <entry>
+ max_reply_timeouts
+ </entry>
+ <entry>
+ -
+ </entry>
+ <entry>
+ Not supported
+ </entry>
+ </row>
+ <row>
+ <entry>
+ recovery_time
+ </entry>
+ <entry>
+ -
+ </entry>
+ <entry>
+ The <literal>ClusterListener</literal> will tell (via a <varname>STATUS</varname> message) mod_cluster that the node is up again
+ </entry>
+ </row>
+ <row>
+ <entry>
+ activation
+ </entry>
+ <entry>
+ -
+ </entry>
+ <entry>
+ mod_cluster receives this information via <varname>ENABLE/DISABLE/STOP</varname> messages
+ </entry>
+ </row>
+ <row>
+ <entry>
+ distance
+ </entry>
+ <entry>
+ -
+ </entry>
+ <entry>
+ mod_cluster handles this via the <varname>loadfactor</varname> logic
+ </entry>
+ </row>
+ <row>
+ <entry>
+ mount
+ </entry>
+ <entry>
+ -
+ </entry>
+ <entry>
+ The context mounted automatically via the <varname>ENABLE-APP</varname> messages. <varname>ProxyPass</varname> could also be used
+ </entry>
+ </row>
+ <row>
+ <entry>
+ secret
+ </entry>
+ <entry>
+ -
+ </entry>
+ <entry>
+ Not supported
+ </entry>
+ </row>
+ <row>
+ <entry>
+ connect_timeout
+ </entry>
+ <entry>
+ -
+ </entry>
+ <entry>
+ Not supported. Use <varname>ProxyTimeout</varname> or server <varname>TimeOut</varname> (Default: 300 seconds)
+ </entry>
+ </row>
+ <row>
+ <entry>
+ prepost_timeout
+ </entry>
+ <entry>
+ ping
+ </entry>
+ <entry>
+ Default: 10 seconds
+ </entry>
+ </row>
+ <row>
+ <entry>
+ reply_timeout
+ </entry>
+ <entry>
+ -
+ </entry>
+ <entry>
+ Not supported. Use <varname>ProxyTimeout</varname> or server <varname>TimeOut?</varname> directive (Default: 300 seconds)
+ </entry>
+ </row>
+ </tbody>
+ </tgroup>
+ </table> -->
+ </section>
+
+
+
+
</chapter>
Modified: projects/docs/enterprise/5.0/mod_cluster/en-US/QuickStartGuide.xml
===================================================================
--- projects/docs/enterprise/5.0/mod_cluster/en-US/QuickStartGuide.xml 2010-02-11 06:29:41 UTC (rev 100856)
+++ projects/docs/enterprise/5.0/mod_cluster/en-US/QuickStartGuide.xml 2010-02-11 07:27:14 UTC (rev 100857)
@@ -18,7 +18,7 @@
If there is no pre-built httpd bundle appropriate for your OS or system architecture, you can build the binary from source.
</para> -->
- <formalpara>
+<!-- <formalpara>
<title>mod_proxy configuration</title>
<para>
mod_proxy directives, such as <command>ProxyIOBufferSize</command>, could be used to configure mod_cluster. There is no need to use <command>ProxyPass</command> directives because mod_cluster automatically configures which URLs have to be forwarded to JBossWEB.
@@ -294,7 +294,7 @@
</para>
</listitem>
</varlistentry>
-</variablelist>
+</variablelist> -->
</section>
@@ -426,6 +426,286 @@
</VirtualHost>
</programlisting>
+
+ <formalpara>
+ <title>mod_proxy configuration</title>
+ <para>
+ mod_proxy directives, such as <command>ProxyIOBufferSize</command>, could be used to configure mod_cluster. There is no need to use <command>ProxyPass</command> directives because mod_cluster automatically configures which URLs have to be forwarded to JBossWEB.
+ </para>
+ </formalpara>
+
+ <formalpara>
+ <title>mod_slotmem configuration</title>
+ <para>
+ The actual version does not require configuration directives.
+ </para>
+ </formalpara>
+
+ <formalpara>
+ <title>mod_proxy_cluster</title>
+ <para>
+
+ </para>
+ </formalpara>
+<variablelist>
+ <varlistentry>
+ <term>CreateBalancers</term>
+ <listitem>
+ <para>
+ Define how the balancers are created in the <literal>httpd VirtualHosts</literal>, this is to allow directives such as the following:
+<screen>
+ProxyPass / balancer://mycluster1/
+</screen>
+ </para>
+ <para>
+<literallayout>Where:
+ 0: Create in all <literal>VirtualHosts</literal> defined in <literal>httpd</literal>.
+ 1: Do not create balancers (requires at least one <varname>ProxyPass/ProxyPassMatch</varname> to define the balancer names).
+ 2: Create only the main server.
+ Default: 2
+</literallayout>
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>UseAlias</term>
+ <listitem>
+ <para>
+ Check that the <filename>Alias</filename> corresponds to the <filename>ServerName</filename> (See Host Name Aliases).
+ </para>
+ <para>
+<literallayout>Where:
+ 0: Do not (ignore Aliases)
+ 1: Check it
+ 2: Default: 0 Ignore the Alias information from the nodes.
+ </literallayout>
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>LBstatusRecalTime </term>
+ <listitem>
+ <para>
+ Time interval in seconds for <varname>loadbalancing</varname> logic to recalculate the status of a node: (Default: 5 seconds)
+ </para>
+ <para>
+ The actual formula to recalculate the status of a node is:
+ </para>
+<programlisting>
+status = lbstatus + (elected - oldelected) * 1000)/lbfactor;
+</programlisting>
+ <para>
+<varname>lbfactor</varname> is received for the node via STATUS messages.
+ </para>
+ <para>
+<varname>lbstatus</varname> is recalculated every <varname>LBstatusRecalTime</varname> seconds using the formula:
+ </para>
+<programlisting>
+lbstatus = (elected - oldelected) * 1000)/lbfactor;
+</programlisting>
+<literallayout>Where:
+ <varname>elected</varname> is the number of times the worker was elected.
+ <varname>oldelected</varname> is elected last time the <varname>lbstatus</varname> was recalculated.
+ The node with the lowest status is selected. Nodes with <varname>lbfactor</varname> ≤ 0 are skipped by the calculation logic.
+ </literallayout>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>ProxyPassMatch/ProxyPass </term>
+ <listitem>
+ <para>
+ <command>ProxyPassMatch</command> and <command>ProxyPass</command> are mod_proxy directives that when using ! (instead of the back-end url), prevent to reverse-proxy in the path.
+ </para>
+ <para>
+ This could be used allow httpd to serve static information, such as images.
+ </para>
+<programlisting>
+ProxyPassMatch ^(/.*\.gif)$ !
+</programlisting>
+ <para>
+ The above, for example, will allow httpd to directly serve the <filename>.gif</filename> files.
+ </para>
+
+ </listitem>
+ </varlistentry>
+</variablelist>
+ <formalpara>
+ <title>mod_manager</title>
+ <para>
+
+ </para>
+ </formalpara>
+<variablelist>
+ <varlistentry>
+ <term>MemManagerFile</term>
+ <listitem>
+ <para>
+ <filename>MemManagerFile</filename> is the base name for the names that mod_manager will use to store configuration, generate keys for shared memory or lock files. That must be an absolute path name; the directories will be created if needed. It is highly recommended that those files are placed on a local drive and not an NFS share. Default: <filename class='directory'>$server_root/logs/</filename>
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>Maxnode</term>
+ <listitem>
+ <para>
+ <literal>Maxnode</literal> is the maximum number of nodes supported by mod_cluster. Default: 20
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>Maxhost</term>
+ <listitem>
+ <para>
+ <literal>Maxhost</literal> is the maximum number of hosts (Aliases) supported by mod_cluster. It is also the maximum number of balancers. Default: 10
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>Maxsessionid</term>
+ <listitem>
+ <para>
+ <literal>Maxsessionid</literal> is the number of active <varname>sessionid</varname> we store to give a number of active sessions in the mod_cluster-manager handler. A session is inactive when mod_cluster does not receive any information from the session in 5 minutes. Default: 0 (the logic is activated).
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>ManagerBalancerName</term>
+ <listitem>
+ <para>
+ <filename>ManagerBalancerName</filename> is the name of balancer to use when the JBoss AEP/JBossWeb/Tomcat doesn't provide a balancer name. That is not supported in the current version. (Default value is used). Default: <filename>mycluster</filename>
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>PersistSlots</term>
+ <listitem>
+ <para>
+ Tell <literal>mod_slotmem</literal> to persist the nodes, Alias and Context in files. Default: Off
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>SetHandler mod_cluster-manager</term>
+ <listitem>
+ <para>
+ That is the handler to display the node mod_cluster sees from the cluster. It displays the information about the nodes like <varname>INFO</varname> and additionaly counts the number of active sessions.
+ </para>
+<programlisting><![CDATA[
+ <Location /mod_cluster-manager>
+ SetHandler mod_cluster-manager
+
+ Order deny,allow
+ Deny from all
+ Allow from 127.0.0.1
+ </Location>
+]]></programlisting>
+ </listitem>
+ </varlistentry>
+</variablelist>
+
+ <note>
+<variablelist>
+ <varlistentry>
+ <term>Transferred</term>
+ <listitem>
+ <para>
+ Corresponds to the <varname>POST</varname> data sent to the back-end server.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>Connected</term>
+ <listitem>
+ <para>
+ Corresponds to the number of requests processed when the mod_cluster status page was requested.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>sessions</term>
+ <listitem>
+ <para>
+ Corresponds to the number of sessions mod_cluster report as active (on which there was a request during the past 5 minutes). That field is not present when <varname>Maxsessionid</varname> is zero.
+ </para>
+ </listitem>
+ </varlistentry>
+</variablelist>
+ </note>
+
+ <formalpara>
+ <title>mod_advertise</title>
+ <para>
+ <varname>mod_advertise</varname> uses multicast packets to advertise the <literal>VirtualHost</literal> where it is configured that must be the same VirtualHost where mod_manager is defined. At least one <varname>mod_advertise</varname> must be in the VirtualHost to allow mod_cluster to find the right IP and port to provide to the ClusterListener.
+ </para>
+ </formalpara>
+<variablelist>
+ <varlistentry>
+ <term>ServerAdvertise On</term>
+ <listitem>
+ <para>
+ Use the advertise mechanism to tell the JBoss EAP/JBossWeb/Tomcat to whom it should send the cluster information.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>ServerAdvertise On http://hostname:port</term>
+ <listitem>
+ <para>
+ Advise the hostname and port to use. Only needed if the <filename>VirtualHost</filename> is not defined correctly, if the <filename>VirtualHost</filename> is a Name-based Virtual Host or when <filename>VirtualHost</filename> is not used.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>ServerAdvertise Off</term>
+ <listitem>
+ <para>
+ Do not use the advertise mechanism. Default: On.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>AdvertiseGroup IP:port </term>
+ <listitem>
+ <para>
+ That is the multicast address to use (something like 232.0.0.2:8888 for example). IP should correspond to <varname>AdvertiseGroupAddress</varname> and port to <literal>AdvertisePort</literal> in the JBoss EAP/JBossWeb/Tomcat configuration. Note that if JBoss EAP is used and the <literal>-u</literal> startup switch is included in the EAP startup command, the default <varname>AdvertiseGroupAddress</varname> is the value passed via the <literal>-u</literal>. Default: 224.0.1.105:23364. If port is missing the default port will be used: 23364.
+ </para>
+ </listitem>
+</varlistentry>
+<varlistentry>
+ <term>AdvertiseFrequency seconds[.miliseconds]</term>
+ <listitem>
+ <para>
+ Time between the multicast messages advertising the IP and port. Default: 10 Ten seconds.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>AdvertiseSecurityKey value</term>
+ <listitem>
+ <para>
+ The key string to identify the mod_cluster in JBossWEB. Default: No default value. Information not sent.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>AdvertiseManagerUrl value</term>
+ <listitem>
+ <para>
+ Not used in this version (It is sent in the X-Manager-Url: value header). That is the URL that JBoss EAP/JBossWeb/Tomcat should use to send information to mod_cluster. Default: No default value. Information not sent.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>AdvertiseBindAddress IP:port </term>
+ <listitem>
+ <para>
+ It is the address and port httpd binds to send the multicast messages. This allows to specify an address on multi IP address boxes. Default: 0.0.0.0:23364
+ </para>
+ </listitem>
+ </varlistentry>
+</variablelist>
+
+
</section>
<section id="sect-mod_cluster-Quick_Start_Guide-Install_the_Java_side_binaries">
@@ -602,7 +882,7 @@
<itemizedlist>
<listitem>
<para>
- A primary servlet that responds to client requests with the value of the <varname>jvmRoute</varname> attribute of the <filename>server.xml</filename> file's Engine element. This response allows the client application to track which servers are handling requests.<filename>mod_proxy.so</filename>
+ A primary servlet that responds to client requests with the value of the <varname>jvmRoute</varname> attribute of the <filename>server.xml</filename> file's Engine element. This response allows the client application to track which servers are handling requests.
</para>
</listitem>
<listitem>
@@ -676,8 +956,8 @@
On *nix
<programlisting>
-[bes at besdev ~]$ cd /home/bes/mod_cluster/demo/client
-[bes at besdev mod_cluster]$ ./run-demo.sh
+[user at machine ~]$ cd /home/user/mod_cluster/demo/client
+[user at machine client]$ ./run-demo.sh
</programlisting>
</para>
</listitem>
@@ -706,7 +986,7 @@
</listitem>
<listitem>
<para>
- Switch to the "Session Balancing" tab to see how many active <literal>sessions2</literal> are being hosted by each of your JBossEAP/JBossWeb/Tomcat servers.
+ Switch to the "Session Balancing" tab to see how many active <literal>sessions</literal> are being hosted by each of your JBossEAP/JBossWeb/Tomcat servers.
</para>
</listitem>
<listitem>
@@ -773,7 +1053,7 @@
<term>Invalidate</term>
<listitem>
<para>
- Controls what the client thread should do when it stops using a session because <menuchoice><guimenuitem>Session Life</guimenuitem></menuchoice> has passed. If checked, the driver will send a request that results in the session being invalidated. If unchecked, the session will just be abandoned, and will continue to exist on the server until <menuchoice><guimenuitem>Session Timeout</guimenuitem></menuchoice> seconds have passed. (In the future this will likely be changed to a percentage input, so X% can be invalidated, the rest abandoned.)
+ Controls what the client thread should do when it stops using a session because <menuchoice><guimenuitem>Session Life</guimenuitem></menuchoice> has passed. If checked, the driver will send a request that results in the session being invalidated. If unchecked, the session will just be abandoned, and will continue to exist on the server until <menuchoice><guimenuitem>Session Timeout</guimenuitem></menuchoice> seconds have passed.
</para>
</listitem>
</varlistentry>
@@ -904,8 +1184,6 @@
</varlistentry>
</variablelist>
-
-
</section>
</chapter>
Modified: projects/docs/enterprise/5.0/mod_cluster/en-US/Revision_History.xml
===================================================================
--- projects/docs/enterprise/5.0/mod_cluster/en-US/Revision_History.xml 2010-02-11 06:29:41 UTC (rev 100856)
+++ projects/docs/enterprise/5.0/mod_cluster/en-US/Revision_History.xml 2010-02-11 07:27:14 UTC (rev 100857)
@@ -6,8 +6,8 @@
<simpara>
<revhistory>
<revision>
- <revnumber>1.9</revnumber>
- <date>Tue 09 Feb 2010</date>
+ <revnumber>2.0</revnumber>
+ <date>Thurs 11 Feb 2010</date>
<author>
<firstname>Gary</firstname>
<surname>Meintjes</surname>
More information about the jboss-cvs-commits
mailing list