[jboss-cvs] JBossAS SVN: r100241 - projects/docs/enterprise/5.0/mod_cluster/en-US.
jboss-cvs-commits at lists.jboss.org
jboss-cvs-commits at lists.jboss.org
Tue Feb 2 01:28:22 EST 2010
Author: gmeintjes
Date: 2010-02-02 01:28:21 -0500 (Tue, 02 Feb 2010)
New Revision: 100241
Modified:
projects/docs/enterprise/5.0/mod_cluster/en-US/Book_Info.xml
projects/docs/enterprise/5.0/mod_cluster/en-US/Overview.xml
projects/docs/enterprise/5.0/mod_cluster/en-US/QuickStartGuide.xml
projects/docs/enterprise/5.0/mod_cluster/en-US/Revision_History.xml
projects/docs/enterprise/5.0/mod_cluster/en-US/mod_cluster.xml
Log:
Amend to reflect comments from review.
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-02 06:14:27 UTC (rev 100240)
+++ projects/docs/enterprise/5.0/mod_cluster/en-US/Book_Info.xml 2010-02-02 06:28:21 UTC (rev 100241)
@@ -3,11 +3,11 @@
]>
<bookinfo id="book-mod_cluster-mod_cluster">
<title>mod_cluster</title>
- <subtitle>for Use with JBoss Enterprise Application Platform 5</subtitle>
+ <subtitle>for Use with JBoss Enterprise Application Platform 5.0</subtitle>
<productname>JBoss Enterprise Application Platform</productname>
- <productnumber>0.1</productnumber>
+ <productnumber>5.0</productnumber>
<edition>1</edition>
- <pubsnumber>1.3</pubsnumber>
+ <pubsnumber>1.5</pubsnumber>
<abstract>
<para>
mod_cluster is an httpd-based load balancer that uses a
Modified: projects/docs/enterprise/5.0/mod_cluster/en-US/Overview.xml
===================================================================
--- projects/docs/enterprise/5.0/mod_cluster/en-US/Overview.xml 2010-02-02 06:14:27 UTC (rev 100240)
+++ projects/docs/enterprise/5.0/mod_cluster/en-US/Overview.xml 2010-02-02 06:28:21 UTC (rev 100241)
@@ -21,19 +21,29 @@
<itemizedlist>
<listitem>
<para>
- <application>RHEL4.5 x86, x64</application>
+ <application>RHEL5 i386, x86_64</application>
</para>
</listitem>
<listitem>
<para>
- <application>Solaris x86, x64</application>
+ <application>RHEL4 i386, x86_64</application>
</para>
</listitem>
<listitem>
<para>
- <application>Windows x86, x64</application>
+ <application>Solaris 10 i386, x86_64</application>
</para>
</listitem>
+ <listitem>
+ <para>
+ <application>Solaris 9 i386</application>
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <application>Windows i386, x86_64</application>
+ </para>
+ </listitem>
</itemizedlist>
</section>
@@ -76,12 +86,12 @@
<itemizedlist>
<listitem>
<para>
- httpd-2.2.8+
+ <application>httpd-2.2.8+</application>
</para>
</listitem>
<listitem>
<para>
- <application>JBossAS 5.0.0+</application>
+ <application>JBoss EAP 5.0+</application>
</para>
</listitem>
</itemizedlist>
@@ -95,7 +105,7 @@
<section id="sect-mod_cluster-Overview-Configuration">
<title>Configuration</title>
<para>
- To configure for JBossAS, refer to the relavant chapter in this publication.
+ To configure for JBoss EAP, refer to the relavant chapter in this publication.
</para>
</section>
@@ -109,7 +119,7 @@
<section id="sect-mod_cluster-Overview-Load_Balancing_Demo_Application">
<title>Load Balancing Demo Application</title>
<para>
- The mod_cluster binary distribution for JBoss AS includes a demo application that helps demonstrate how different server-side scenarios affect the routing of client requests by the load balancer. The demo application is located in the mod_cluster distribution's demo directory.
+ The mod_cluster binary distribution for JBoss EAP includes a demo application that helps demonstrate how different server-side scenarios affect the routing of client requests by the load balancer. The demo application is located in the mod_cluster distribution's demo directory.
</para>
</section>
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-02 06:14:27 UTC (rev 100240)
+++ projects/docs/enterprise/5.0/mod_cluster/en-US/QuickStartGuide.xml 2010-02-02 06:28:21 UTC (rev 100241)
@@ -7,13 +7,16 @@
The following steps are required to set up a minimal working installation of mod_cluster on a single httpd server and a single back end server, either <application>JBoss AS</application>, <application>JBossWeb</application> or <application>Tomcat</application>. The steps can be repeated to add as many httpd servers or back end servers to your cluster as desired.
</para>
<para>
- The steps shown here are not intended to demonstrate how to set up a production install of mod_cluster; for example using <application>SSL</application> to secure access to the httpd-side mod_manager component is not covered. See the <citetitle>httpd-side</citetitle> and <citetitle>java-side configuration documentation</citetitle> for the full set of configuration options.
+ The steps shown here are not intended to demonstrate how to set up a production install of mod_cluster; for example using <application>SSL</application> to secure access to the httpd-side mod_manager component is not covered. See the <citetitle>httpd-side</citetitle> and <citetitle>Java-side configuration documentation</citetitle> for the full set of configuration options.
</para>
<section id="sect-mod_cluster-Quick_Start_Guide-Download_mod_cluster_components">
<title>Download mod-cluster components</title>
<para>
- Download the latest httpd and java release bundles. If there is no pre-built httpd bundle appropriate for your OS or system architecture, you can build the binary from source.
- </para>
+ Download the latest httpd and Java release bundles.
+ </para>
+ <!-- <para>
+ If there is no pre-built httpd bundle appropriate for your OS or system architecture, you can build the binary from source.
+ </para> -->
</section>
<section id="sect-mod_cluster-Quick_Start_Guide-Install_the_httpd_binary">
@@ -41,8 +44,10 @@
<programlisting>
cd /tmp
-tar xvf mod_cluster-1.0.0.CR2-linux2-x86-so.tar.gz
+unzip jboss-eap-native-5.0.0-mod-cluster-RHEL5-x86_64.zip
+<!-- tar xvf mod_cluster-1.0.0.CR2-linux2-x86-so.tar.gz -->
</programlisting>
+
<para>
Then copy the following files to the module directory.
</para>
@@ -147,20 +152,20 @@
<section id="sect-mod_cluster-Quick_Start_Guide-Install_the_Java_side_binaries">
<title>Install the Java-side binaries</title>
<para>
- Extract the java-side binary to a temporary directory. The following assumes it was extracted to <filename>/tmp/mod-cluster</filename>.
+ Extract the Java-side binary to a temporary directory. The following assumes it was extracted to <filename>/tmp/mod-cluster</filename>.
</para>
<para>
- The next step depends on whether your target server is JBoss AS or JBossWeb/Tomcat.
+ The next step depends on whether your target server is JBoss EAP or JBossWeb/Tomcat.
</para>
<formalpara id="form-mod_cluster-Install_the_Java_side_binaries-Installing_in_JBoss_AS_5.x_and_up">
- <title>Installing in JBoss AS 5.x and up</title>
+ <title>Installing in JBoss EAP 5.0</title>
<para>
- Assume that <filename>$JBOSS_HOME </filename> indicates the root of your JBoss AS install and that you want to use mod_cluster in the AS <literal>all</literal> config:
+ Assume that <filename>$JBOSS_HOME </filename> indicates the root of your JBoss EAP install and that you want to use mod_cluster in the <literal>production</literal> profile:
</para>
</formalpara>
<programlisting>
-cp -r /tmp/mod-cluster/mod-cluster.sar $JBOSS_HOME/server/all/deploy
+cp -r /tmp/mod-cluster/mod-cluster.sar $JBOSS_HOME/server/production/deploy
</programlisting>
<formalpara id="form-mod_cluster-Install_the_Java_side_binaries-Installing_in_JBoss_Web_or_Tomcat">
<title>Installing in JBoss Web or Tomcat</title>
@@ -172,32 +177,32 @@
<programlisting>
cp -r /tmp/mod-cluster/JBossWeb-Tomcat/lib/* $CATALINA_HOME/lib/
</programlisting>
- <formalpara id="form-mod_cluster-Install_the_Java_side_binaries-Installing_in_JBoss_AS_4.2.x_or_4.3.x">
- <title>Installing in JBoss AS 4.2.x or 4.3.x</title>
+ <!--<formalpara id="form-mod_cluster-Install_the_Java_side_binaries-Installing_in_JBoss_AS_4.2.x_or_4.3.x">
+ <title>Installing in JBoss AS 4.2.x or 4.3.x</title>
<para>
- Assuming <filename>$JBOSS_HOME</filename> indicates the root of your JBoss AS install and that you want to use mod_cluster in the AS <literal>all</literal> config:
+ Assuming <filename>$JBOSS_HOME</filename> indicates the root of your JBoss EAP install and that you want to use mod_cluster in the <literal>production</literal> profile:
</para>
</formalpara>
<programlisting>
cp -r /tmp/mod-cluster/JBossWeb-Tomcat/lib/mod-cluster.jar $JBOSS_HOME/server/all/deploy/jboss-web.deployer
-</programlisting>
+</programlisting> -->
</section>
<section id="sect-mod_cluster-Quick_Start_Guide-Configuring_JBoss_AS_JBoss_Web_or_Tomcat">
- <title>Configuring JBoss AS, JBoss Web or Tomcat</title>
+ <title>Configuring JBoss EAP, JBoss Web or Tomcat</title>
<para>
mod_cluster is integrated into the web server by adding an implementation of the <application>Tomcat LifecycleListener</application> interface to the server's configuration, and by giving each node a unique name.
</para>
<formalpara id="form-mod_cluster-Configuring_JBoss_AS_JBoss_Web_or_Tomcat-Integrate_mod_cluster_with_JBoss_ASs_embedded_JBossWeb">
<title>Integrate mod_cluster with JBoss AS's embedded JBossWeb</title>
<para>
- Assuming <filename>$JBOSS_HOME</filename> indicates the root of your JBoss AS install and that you want to use mod_cluster in the AS's <literal>all</literal> config:
+ Assuming <filename>$JBOSS_HOME</filename> indicates the root of your JBoss AS install and that you want to use mod_cluster in the <literal>production</literal> profile:
<orderedlist>
<listitem>
<para>
- Edit the <filename>$JBOSS_HOME/server/all/deploy/jbossweb.sar/server.xml</filename> file, adding the following next to the other <application>LifecycleListener</application> elements:
- </para>
+ Edit the <filename>$JBOSS_HOME/server/production/deploy/jbossweb.sar/server.xml</filename> file, adding the following next to the other <application>LifecycleListener</application> elements:
+ </para>
<screen>
<Listener className="org.jboss.web.tomcat.service.deployers.MicrocontainerIntegrationLifecycleListener"
@@ -206,11 +211,11 @@
</listitem>
<listitem>
<para>
- Edit the <filename>$JBOSS_HOME/server/all/deploy/jbossweb.sar/META-INF/jboss-beans.xml</filename> file, adding the following next to the other <application>depends</application> elements:
+ Edit the <filename>$JBOSS_HOME/server/production/deploy/jbossweb.sar/META-INF/jboss-beans.xml</filename> file, adding the following next to the other <application>depends</application> elements:
</para>
<screen>
- <depends>ModClusterService</depends/>
+ <depends>ModClusterService<depends/>
</screen>
</listitem>
</orderedlist>
@@ -227,12 +232,12 @@
<Listener className="org.jboss.modcluster.ModClusterListener"
advertise="true"/>
</programlisting>
- <formalpara id="form-mod_cluster-Configuring_JBoss_AS_JBoss_Web_or_Tomcat-Integrate_mod_cluster_with_JBoss_AS_4.2.x_and_4.3.x">
+ <!-- <formalpara id="form-mod_cluster-Configuring_JBoss_AS_JBoss_Web_or_Tomcat-Integrate_mod_cluster_with_JBoss_AS_4.2.x_and_4.3.x">
<title>Integrate mod_cluster with JBoss AS 4.2.x and 4.3.x</title>
<para>
Edit the <filename>$JBOSS_HOME/server/all/deploy/jboss-web.deployer/server.xml</filename> file, adding the following next to the other <application>LifecycleListener</application> elements:
</para>
- </formalpara>
+ </formalpara> -->
<programlisting>
<Listener className="org.jboss.modcluster.ModClusterListener"
@@ -260,14 +265,14 @@
</para>
<programlisting>
-/opt/jboss/httpd/sbin/apachectl start
+<!-- /opt/jboss/httpd/sbin/ --> apachectl start
</programlisting>
</section>
<section id="sect-mod_cluster-Quick_Start_Guide-Start_the_back_end_server">
<title>Start the back end server</title>
<formalpara id="form-mod_cluster-Start_the_back_end_server-Starting_JBoss_AS">
- <title>Starting JBoss AS</title>
+ <title>Starting JBoss EAP</title>
<para>
To start <application>JBoss AS</application> enter the following:
</para>
@@ -275,7 +280,7 @@
<programlisting>
cd $JBOSS_HOME/bin
-./run.sh -c all
+./run.sh -c prodution
</programlisting>
<formalpara id="form-mod_cluster-Start_the_back_end_server-Starting_JBossWeb_or_Tomcat">
<title>Starting JBossWeb or Tomcat</title>
@@ -291,9 +296,9 @@
</section>
<section id="sect-mod_cluster-Quick_Start_Guide-Set_up_more_back_end_servers">
- <title>Set up more back end servers</title>
+ <title>Setting up more back end servers</title>
<para>
- Repeat the back end server install and configuration steps; just be sure to use a different jvmRoute for each server.
+ To set up more back end servers, repeat the back end server install and configuration steps; just be sure to use a different jvmRoute for each server.
</para>
</section>
@@ -302,6 +307,388 @@
<para>
The load balancing demo application is a good way to learn about mod_cluster's capabilities.
</para>
+
+ <formalpara>
+ <title>Overview of the Demo Application</title>
+ <para>
+ The mod_cluster distribution includes a demo application that helps demonstrate how different server-side scenarios affect the routing of client requests by the load balancer. The demo application is located in the demo directory of the mod_cluster distribution.
+ </para>
+ </formalpara>
+ <para>
+ The demo application consists of two components:
+ <orderedlist>
+ <listitem>
+ <para>
+ The first component is a war file that needs to be deployed in JBossWeb/Tomcat/JBoss AS. The war includes a number of servlets:
+ <itemizedlist>
+ <listitem>
+ <para>
+ A primary servlet that responds to client requests with the value of the jvmRoute 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>
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ A set of load generation servlets, each of which responds to a request by generating a different type of load (e.g. consuming CPU cycles) on the server on which it is running.
+ </para>
+ </listitem>
+ </itemizedlist>
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ The second component is a GUI application that allows a user to launch a pool of threads that repeatedly make requests to the load balancer. The requests are ultimately routed to the demo war's primary servlet. The application tracks which servers are handling the requests and displays this information in a chart.
+ </para>
+ <para>
+ The application can also send separate requests to the demo war's load generation servlets, allowing the user to see how different load conditions affect the balancing of requests.
+ </para>
+ </listitem>
+ </orderedlist>
+ </para>
+
+ <note>
+ <para>
+ The demo application does not actually depend on mod_cluster in any way. Its only dependency is on JBossWeb/Tomcat.1 So, the demo could be used to demonstrate the effect of different server-side scenarios on the routing decisions made by any load balancer, including mod_jk, mod_proxy or the various hardware load balancers.
+ </para>
+ </note>
+ <note>
+ <para>
+ This demo application is not intended to be used as a load testing tool; i.e. something that can demonstrate the maximum load a cluster configuration can handle. Using it as such has a greater chance of showing you the maximum load the client can generate rather than the maximum load your cluster can handle.
+ </para>
+ </note>
+
+ <formalpara>
+ <title>Basic Usage</title>
+ <para>
+ Run the demo application as follows:
+ </para>
+ </formalpara>
+ <orderedlist>
+ <listitem>
+ <para>
+ Unpack the mod_cluster distribution on your filesystem. Here we assume it has been unzipped to /home/bes/mod_cluster or C:\mod_cluster.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Install mod_cluster into your httpd server as described at Installation of the httpd part.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Install mod_cluster into your JBossAS/JBossWeb/Tomcat servers as described at Installation on the Java side.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Start httpd and your JBossAS/JBossWeb/Tomcat servers.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Deploy the load-demo.war found in the distribution's demo/server folder to your JBossAS/JBossWeb/Tomcat servers.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Start the demo application:
+ <itemizedlist>
+ <listitem>
+ <para>
+ On *nix
+
+<programlisting>
+[bes at besdev ~]$ cd /home/bes/mod_cluster/demo/client
+[bes at besdev mod_cluster]$ ./run-demo.sh
+</programlisting>
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ On Windows
+<programlisting>
+C:\>cd mod_cluster\demo\client
+C:\mod_cluster\demo\client>run-demo
+</programlisting>
+
+ </para>
+ </listitem>
+ </itemizedlist>
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Configure the hostname and address of the httpd server, the number of client threads, etc and click the "Start" button. See Client Driver Configuration Options for details on the configuration options.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Switch to the "Request Balancing" tab to see how many requests are going to each of your JBoss EAP/JBossWeb/Tomcat servers.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Switch to the "Session Balancing" tab to see how many active sessions2 are being hosted by each of your JBossAS/JBossWeb/Tomcat servers.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Stop some of your JBoss EAP/JBossWeb/Tomcat servers and/or undeploy the load-demo.war from some of the servers and see the effect this has on load balancing.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Restart some of your JBossAS/JBossWeb/Tomcat servers and/or re-deploy the load-demo.war to some of the servers and see the effect this has on load balancing.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Experiment with adding artificial load to one or more servers to see what effect that has on load balancing. See Load Generation Scenarios for details.
+ </para>
+ </listitem>
+ </orderedlist>
+ <para>
+ Most of the various panels in application interface also present information on the current status on any client threads. "Total Clients" is the number of client threads created since the last time the "Start" button was pushed. "Live Clients" is the number of threads currently running. "Failed Clients" is the number of clients that terminated abnormally; i.e. made a request that resulted in something other than an HTTP 200 response.
+ </para>
+
+ <formalpara>
+ <title>Client Driver Configuration Options</title>
+ <para>
+ The configuration of the client is driver is done via the application's "Client Control" tab.
+ </para>
+ </formalpara>
+ <para>
+ The panel includes the following options:
+ </para>
+<variablelist>
+ <varlistentry>
+ <term>Proxy Hostname</term>
+ <listitem>
+ <para>
+ Hostname of the load balancer or the IP address on which it is listening for requests
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>Proxy Port</term>
+ <listitem>
+ <para>Port on which the load balancer is listening for requests</para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>Context Path</term>
+ <listitem>
+ <para>
+ Portion of the request URL that specifies the request is for the load-demo.war
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>Session Life</term>
+ <listitem>
+ <para>
+ Number of seconds a client thread should use a session before invalidating or abandoning it. Generally it is good to keep this to a small value; otherwise the use of session stickiness will prevent changes in server load from affecting the load balancer's routing decisions. With sticky sessions enabled (strongly recommended), it is the creation of a new session that allows the load balancer to try to balance load.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>Invalidate</term>
+ <listitem>
+ <para>
+ Controls what the client thread should do when it stops using a session because Session Life 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 Session Timeout seconds have passed. (In the future this will likely be changed to a percentage input, so X% can be invalidated, the rest abandoned.)
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>Session Timeout</term>
+ <listitem>
+ <para>Number of seconds a session can remain unused before the server is free to expire it. Unchecking Invalidate and setting a high value relative to Session Life allows a significant number of unused sessions to accumulate on the server.</para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>Num Threads</term>
+ <listitem>
+ <para>
+ Number of client threads to launch. Each thread repeatedly makes requests until the "Stop" button is pushed or a request receives a response other than HTTP 200.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>Sleep Time</term>
+ <listitem>
+ <para>
+ Number of ms the client threads should sleep between requests.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>Startup Time</term>
+ <listitem>
+ <para>
+ Number of seconds over which the application should stagger the start of the client threads. Staggering the start is advised as it avoids the unnatural situation where for the life of the demonstation all sessions start at about the same time and then are invalidated or abandoned at the same time. Staggering the start allows the load balancer to continually see new sessions and decide how to route them.
+ </para>
+ </listitem>
+ </varlistentry>
+</variablelist>
+
+ <formalpara>
+ <title>Load Generation Scenarios</title>
+ <para>
+ You can use the application's GUI to instruct individual servers to artificially generate various types of load, and then track how that load affects request and session balancing. Load generation is controlled via the application's "Server Load Control" tab.
+ </para>
+ </formalpara>
+ <para>
+ The panel includes the following options:
+ </para>
+<variablelist>
+ <varlistentry>
+ <term>Target Hostname and Target Port</term>
+ <listitem>
+ <para>
+ The hostname or IP address of the server on which you want load generated. There are two strategies for setting these:
+
+ <orderedlist>
+ <listitem>
+ <para>
+ You can use the hostname and port of the load balancer, in which case the load balancer will pick a backend server and route the request to it. Note the client application does not maintain a session cookie for these requests, so if you invoke another server load generation request, you shouldn't expect the same server to handle it.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ If the JBoss AS/JBossWeb/Tomcat servers are running the HttpConnector as well as the AJP connector, you can specify the address and port on which a particular server's HttpConnector is listening. The standard port is 8080.
+ </para>
+ </listitem>
+ </orderedlist>
+
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>Load Creation Action</term>
+ <listitem>
+ <para>
+ Specifies the type of load the target server should generate. See below for details on the available load types.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>Params</term>
+ <listitem>
+ <para>
+ Zero or more parameters to pass to the specified load creation servlet. For example, in the screenshot above, Number of Connections and Duration. How many parameters are displayed, their name and their meaning depend on the selected Load Creation Action. The label for each parameter includes a tooltip that explains its use.
+ </para>
+ <para>
+ The available Load Creation Actions are as follows:
+ <orderedlist>
+ <listitem>
+ <para>
+ Active Sessions: Generates server load by causing session creation on the target server.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Datasource Use: Generates server load by taking connections from the java:DefaultDS datasource for a period.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Connection Pool Use: Generates server load by tieing up threads in the webserver connections pool for a period.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Heap Memory Pool Use: Generates server load by filling 50% of free heap memory for a period.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ CPU Use: Generates server CPU load by initiating a tight loop in a thread.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Server Receive Traffic: Generates server traffic receipt load by POSTing a large byte array to the server once per second for a period.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Server Send Traffic: Generates server traffic send load by making a request once per second to which the server responds with a large byte array
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Request Count: Generates server load by making numerous requests, increasing the request count on the target server.
+ </para>
+ </listitem>
+ </orderedlist>
+ </para>
+ </listitem>
+ </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-02 06:14:27 UTC (rev 100240)
+++ projects/docs/enterprise/5.0/mod_cluster/en-US/Revision_History.xml 2010-02-02 06:28:21 UTC (rev 100241)
@@ -6,8 +6,8 @@
<simpara>
<revhistory>
<revision>
- <revnumber>1.2</revnumber>
- <date>Thursday Jan 07 2010</date>
+ <revnumber>1.5</revnumber>
+ <date>Tue 02 Feb 2010</date>
<author>
<firstname>Gary</firstname>
<surname>Meintjes</surname>
@@ -15,7 +15,7 @@
</author>
<revdescription>
<simplelist>
- <member>Initial formatting of book for publishing with Publican</member>
+ <member>Amend publication as per review comments</member>
</simplelist>
</revdescription>
</revision>
Modified: projects/docs/enterprise/5.0/mod_cluster/en-US/mod_cluster.xml
===================================================================
--- projects/docs/enterprise/5.0/mod_cluster/en-US/mod_cluster.xml 2010-02-02 06:14:27 UTC (rev 100240)
+++ projects/docs/enterprise/5.0/mod_cluster/en-US/mod_cluster.xml 2010-02-02 06:28:21 UTC (rev 100241)
@@ -7,8 +7,8 @@
<!-- <xi:include href="Chapter.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> -->
<xi:include href="Overview.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
<xi:include href="QuickStartGuide.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
+ <xi:include href="MigratingFromModJK.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
<xi:include href="ConfigurationForJBossAS.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
- <xi:include href="MigratingFromModJK.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
<xi:include href="Revision_History.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
<index />
</book>
More information about the jboss-cvs-commits
mailing list