[jboss-cvs] JBossAS SVN: r99091 - projects/docs/enterprise/5.0/mod_cluster/en-US.
jboss-cvs-commits at lists.jboss.org
jboss-cvs-commits at lists.jboss.org
Thu Jan 7 00:24:05 EST 2010
Author: gmeintjes
Date: 2010-01-07 00:24:02 -0500 (Thu, 07 Jan 2010)
New Revision: 99091
Modified:
projects/docs/enterprise/5.0/mod_cluster/en-US/Author_Group.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/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
Log:
amended as per tech review redlines
Modified: projects/docs/enterprise/5.0/mod_cluster/en-US/Author_Group.xml
===================================================================
--- projects/docs/enterprise/5.0/mod_cluster/en-US/Author_Group.xml 2010-01-07 04:54:46 UTC (rev 99090)
+++ projects/docs/enterprise/5.0/mod_cluster/en-US/Author_Group.xml 2010-01-07 05:24:02 UTC (rev 99091)
@@ -3,6 +3,31 @@
]>
<authorgroup>
+
+ <othercredit>
+ <firstname>Permaine</firstname>
+ <surname>Cheung</surname>
+ <contrib>Technical Review
+ </contrib>
+ </othercredit>
+
+
+ <othercredit>
+ <firstname>Paul</firstname>
+ <surname>Ferraro</surname>
+ <contrib>Technical Review
+ </contrib>
+ </othercredit>
+
+
+ <othercredit>
+ <firstname>Radoslav</firstname>
+ <surname>Husar</surname>
+ <contrib>Technical Review
+ </contrib>
+ </othercredit>
+
+
<editor>
<firstname>Gary</firstname>
<surname>Meintjes</surname>
@@ -12,4 +37,8 @@
</affiliation>
<email>gmeintje at redhat.com</email>
</editor>
-</authorgroup>
\ No newline at end of file
+
+
+
+
+</authorgroup>
Modified: projects/docs/enterprise/5.0/mod_cluster/en-US/ConfigurationForJBossAS.xml
===================================================================
--- projects/docs/enterprise/5.0/mod_cluster/en-US/ConfigurationForJBossAS.xml 2010-01-07 04:54:46 UTC (rev 99090)
+++ projects/docs/enterprise/5.0/mod_cluster/en-US/ConfigurationForJBossAS.xml 2010-01-07 05:24:02 UTC (rev 99091)
@@ -15,7 +15,7 @@
</para>
<programlisting>
-<filename>$JBOSS_HOME/server/<replaceable>profile/deploy</replaceable>/jbossweb.sar/server.xml</filename>
+<filename>$JBOSS_HOME/server/<replaceable>$PROFILE/deploy</replaceable>/jbossweb.sar/server.xml</filename>
</programlisting>
<formalpara id="form-mod_cluster-Common_Configuration-Add_a_lifecycle_listener.">
<title>Add a lifecycle listener.</title>
@@ -81,7 +81,7 @@
</orderedlist>
</para>
<para>
- To ensure that this delegate bean exists before JBoss Web is started, and does not get destroyed until JBoss Web shuts down, add an explicit microcontainer dependency. Update the WebServer bean contained in <filename>$JBOSS_HOME/server/<literal>profile</literal>/deploy/jbossweb.sar/META-INF/jboss-beans.xml</filename> with an appropriate dependency:
+ To ensure that this delegate bean exists before JBoss Web is started, and does not get destroyed until JBoss Web shuts down, add an explicit microcontainer dependency. Update the WebServer bean contained in <filename>$JBOSS_HOME/server/<literal>$PROFILE</literal>/deploy/jbossweb.sar/META-INF/jboss-beans.xml</filename> with an appropriate dependency:
</para>
<programlisting>
@@ -99,7 +99,7 @@
<Listener lassName="org.jboss.web.tomcat.service.deployers.MicrocontainerIntegrationLifecycleListener" delegateBeanName="ModClusterService"/>
</programlisting>
<para>
- The ModClusterService bean descriptor is found in the following file: <filename>$JBOSS_HOME/server/profile/deploy/mod-cluster.sar/META-INF/mod-cluster-jboss-beans.xml</filename>
+ The ModClusterService bean descriptor is found in the following file: <filename>$JBOSS_HOME/server/$PROFILE/deploy/mod-cluster.sar/META-INF/mod-cluster-jboss-beans.xml</filename>
</para>
<programlisting>
@@ -150,6 +150,7 @@
</para>
</listitem>
</itemizedlist>
+
</section>
<section id="sect-mod_cluster-Configuring_for_JBoss_AS-Clustered_Mode">
@@ -181,10 +182,10 @@
If your application server already uses other clustering services (e.g. session replication), then you should consider running mod_cluster in clustered-mode. If your application server is stateless (i.e. no sessions), or you are not using other clustering services, then non-clustered mode may be more appropriate.
</para>
<para>
- The HAModClusterService bean descriptor is found in the following file:
+ The <classname>HAModClusterService</classname> bean descriptor is found in the following file:
</para>
<para>
- $JBOSS_HOME/server/profile/deploy/mod-cluster.sar/META-INF/mod-cluster-jboss-beans.xml
+ <filename>$JBOSS_HOME/server/$PROFILE/deploy/mod-cluster.sar/META-INF/mod-cluster-jboss-beans.xml</filename>
</para>
<programlisting>
@@ -205,23 +206,20 @@
<para>
The <classname>HAModClusterService</classname> bean defines:
</para>
- <!-- <variablelist>
- <varlistentry><term>An <classname>HAPartition</classname> instance</term>
+ <variablelist>
+ <varlistentry><term>An <classname>HAPartition</classname> instance</term>
<listitem>
<para>
An <classname>HAPartition</classname> is an abstraction defining the nodes a singleton master will manage. The default <classname>HAPartition</classname> is defined in:
-<filename>$JBOSS_HOME/server/profile/deploy/cluster/cluster-jboss-beans.xml</filename>
+<filename>$JBOSS_HOME/server/$PROFILE/deploy/cluster/cluster-jboss-beans.xml</filename>
</para>
</listitem>
</varlistentry>
- <varlistentry><term>An <object>HAModClusterConfig</object> bean, defining containing the configuration properties.</term>
+ <varlistentry><term>An <classname>HAModClusterConfig</classname> bean, defining containing the configuration properties.</term>
<listitem>
<para>
For the complete list of configuration properties available to ModClusterService, refer to the following sections:
- </para>
- </listitem>
- </varlistentry>
- </variablelist> --><!-- <itemizedlist>
+ <itemizedlist>
<listitem>
<para>
Proxy Discovery configuration
@@ -242,7 +240,14 @@
HA configuration
</para>
</listitem>
- </itemizedlist> --><!-- <variablelist>
+ </itemizedlist>
+
+ </para>
+ </listitem>
+ </varlistentry>
+ </variablelist>
+
+ <variablelist>
<varlistentry><term>A load balance factor provider</term>
<listitem>
<para>
@@ -257,8 +262,1079 @@
</para>
</listitem>
</varlistentry>
- </variablelist> -->
+ </variablelist>
</section>
+ <section>
+ <title>Configuration Properties</title>
+ <para> The following configuration properties are available to an application server node. The location for their properties depends on the mod_cluster configuration.
+ </para>
+ <formalpara>
+ <title>Discovery Configuration
+ </title>
+ <para> The list of proxies from which an application expects to receive AJP connections is either defined statically, via the addresses defined in the proxyList configuration property; or discovered dynamically via the advertise mechanism. Using a special mod_advertise module, proxies can advertise their existence by periodically broadcasting a multicast message containing its address/port. This functionality is enabled via the advertise configuration property. If configured to listen, a server can learn of the proxy's existence, then notify that proxy of its own existence, and update its configuration accordingly. This frees both the proxy and the server from having to define static, environment-specific configuration values.
+ </para>
+ </formalpara>
+
+ <table frame="all">
+ <title>Proxy Discovery Configuration</title>
+ <tgroup colsep="1" cols="3">
+ <colspec colname="c1"/>
+ <colspec colname="c2"/>
+ <colspec colname="c3"/>
+ <thead>
+ <row>
+ <entry>Attribute</entry>
+ <entry>Default</entry>
+ <entry>Description</entry>
+ </row>
+ </thead>
+ <tbody>
+ <row>
+ <entry>
+<property>proxyList</property>
+ </entry>
+ <entry>
+<emphasis>None</emphasis>
+ </entry>
+ <entry>
+Defines a comma delimited list of httpd proxies with which this node will initially communicate. Value should be of the form:
+
+<varname>address1:port1, address2:port2</varname>
+Using the default configuration, this property can by manipulated via the <varname>jboss.modcluster.proxyList</varname> system property.
+ </entry>
+ </row>
+ <row>
+ <entry>
+<property>excludedContexts</property>
+ </entry>
+ <entry>
+ROOT,invoker,jbossws,jmx-console,juddi,web-console
+ </entry>
+ <entry>
+List of contexts to exclude from httpd registration, of the form:
+<varname>host1:context1, host2:context2, host3:context3</varname>
+If no host is indicated, it is assumed to be the default host of the server (e.g. localhost). "ROOT" indicates the root context. Using the default configuration, this property can by manipulated via the <varname>jboss.modcluster. excludedContexts</varname> system property.
+ </entry>
+ </row>
+ <row>
+ <entry>
+<property>proxyURL</property>
+ </entry>
+ <entry>
+<emphasis>None</emphasis>
+ </entry>
+ <entry>
+If defined, this value will be prepended to the URL of MCMP commands.
+ </entry>
+ </row>
+ <row>
+ <entry>
+<property>socketTimeout</property>
+ </entry>
+ <entry>
+20000
+ </entry>
+ <entry>
+Number of milliseconds to wait for a response from an httpd proxy to MCMP commands before timing out, and flagging the proxy as in error.
+ </entry>
+ </row>
+ <row>
+ <entry>
+<property>advertise</property>
+ </entry>
+ <entry>
+<emphasis>true, if proxyList is undefined, false otherwise</emphasis>
+ </entry>
+ <entry>
+If enabled, httpd proxies will be auto-discovered via multicast announcements. This can be used either in concert or in place of a static proxyList.
+ </entry>
+ </row>
+ <row>
+ <entry>
+<property>advertise</property>
+ </entry>
+ <entry>
+224.0.1.105
+ </entry>
+ <entry>
+UDP address on which to listen for httpd proxy multicast advertisements .
+ </entry>
+ </row>
+ <row>
+ <entry>
+<property>advertisePort</property>
+ </entry>
+ <entry>
+23364
+ </entry>
+ <entry>
+UDP port on which to listen for httpd proxy multicast advertisements.
+ </entry>
+ </row>
+ <row>
+ <entry>
+<property>advertiseSecurityKey</property>
+ </entry>
+ <entry>
+<emphasis>None</emphasis>
+ </entry>
+ <entry>
+If specified, httpd proxy advertisements checksums will be verified using this value as a salt.
+ </entry>
+ </row>
+ </tbody>
+ </tgroup>
+ </table>
+
+ <formalpara>
+ <title>Proxy Configuration
+ </title>
+ <para> The following configuration values are sent to proxies during server startup, when a proxy is detected via the advertise mechanism, or during the resetting of a proxy's configuration during error recovery.
+ </para>
+ </formalpara>
+
+ <table frame="all">
+ <title>Proxy Configuration</title>
+ <tgroup colsep="1" cols="3">
+ <colspec colname="c1"/>
+ <colspec colname="c2"/>
+ <colspec colname="c3"/>
+ <thead>
+ <row>
+ <entry>Attribute</entry>
+ <entry>Default</entry>
+ <entry>Description</entry>
+ </row>
+ </thead>
+ <tbody>
+ <row>
+ <entry>
+<property>stickySession</property>
+ </entry>
+ <entry>
+<literal>true</literal>
+ </entry>
+ <entry>
+Indicates whether subsequent requests for a given session should be routed to the same node, if possible.
+ </entry>
+ </row>
+ <row>
+ <entry>
+<property>stickySessionRemove</property>
+ </entry>
+ <entry>
+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.
+ </entry>
+ </row>
+ <row>
+ <entry>
+<property>stickySessionForce</property>
+ </entry>
+ <entry>
+true
+ </entry>
+ <entry>
+Indicates whether the httpd proxy should return an error 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>
+ <entry>
+<property>workerTimeout</property>
+ </entry>
+ <entry>
+-1
+ </entry>
+ <entry>
+Number of seconds to wait for a worker to become available to handle a request. When all the workers of a balancer are usable, mod_cluster will retry after a while (workerTimeout/100) to find an usable worker. That is timeout in the balancer mod_proxy documentation. A value of -1 indicates that the httpd will not wait for a worker to be available and will return an error if none is available.
+ </entry>
+ </row>
+ <row>
+ <entry>
+<property>maxAttempts</property>
+ </entry>
+ <entry>
+1
+ </entry>
+ <entry>
+Number of times an httpd proxy will attempt to send a given request to a worker before giving up. The minimum value is 1, meaning try only once. (Note that mod_proxy default is also 1: no retry).
+ </entry>
+ </row>
+ <row>
+ <entry>
+<property>flushPackets</property>
+ </entry>
+ <entry>
+false
+ </entry>
+ <entry>
+Enables/disables packet flushing.
+ </entry>
+ </row>
+ <row>
+ <entry>
+<property>flushWait</property>
+ </entry>
+ <entry>
+-1
+ </entry>
+ <entry>
+Time to wait before flushing packets. A value of -1 means wait forever.
+ </entry>
+ </row>
+ <row>
+ <entry>
+<property>ping</property>
+ </entry>
+ <entry>
+10 seconds
+ </entry>
+ <entry>
+Time to wait for a pong answer to a ping
+ </entry>
+ </row>
+ <row>
+ <entry>
+<property>smax</property>
+ </entry>
+ <entry>
+Determined by httpd configuration
+ </entry>
+ <entry>
+Soft maximum idle connection count (that is the smax in worker mod_proxy documentation). The maximum value depends on the httpd thread configuration (ThreadsPerChild or 1).
+ </entry>
+ </row>
+ <row>
+ <entry>
+<property>ttl</property>
+ </entry>
+ <entry>
+60 seconds
+ </entry>
+ <entry>
+Time to live (in seconds) for idle connections above smax
+ </entry>
+ </row>
+ <row>
+ <entry>
+<property>nodeTimeout</property>
+ </entry>
+ <entry>
+-1 (none)
+ </entry>
+ <entry>
+Timeout (in seconds) for proxy connections to a node. That is the time mod_cluster will wait for the back-end response before returning error. That corresponds to timeout in the worker mod_proxy documentation. Note that mod_cluster always uses a cping/cpong before forwarding a request and the connectiontimeout value used by mod_cluster is the ping value.
+ </entry>
+ </row>
+ <row>
+ <entry>
+<property>balancer</property>
+ </entry>
+ <entry>
+mycluster
+ </entry>
+ <entry>
+The balancer name
+ </entry>
+ </row>
+ <row>
+ <entry>
+<property>domain</property>
+ </entry>
+ <entry>
+<emphasis>None</emphasis>
+ </entry>
+ <entry>
+If specified, load will be balanced among jvmRoutes with the same domain. This is primarily used in conjunction with partitioned session replication (e.g. buddy replication).
+ </entry>
+ </row>
+ </tbody>
+ </tgroup>
+ </table>
+<note>
+ <title>Timeout not defined
+ </title>
+ <para>When nodeTimeout is not defined the ProxyTimeout directive Proxy is used. If ProxyTimeout is not defined the server timeout (Timeout) is used (default 300 seconds). nodeTimeout, ProxyTimeout or Timeout is set at the socket level.
+ </para>
+</note>
+ <formalpara>
+ <title>SSL Configuration
+ </title>
+ <para>The communication channel between application servers and httpd proxies uses HTTP by default. This channel can be secured using HTTPS by setting the ssl to true.
+ </para>
+ </formalpara>
+<note>
+ <title>HTTP/HTTPS channel
+ </title>
+ <para>This HTTP/HTTPS channel should not be confused with the processing of HTTP/HTTPS client requests.
+ </para>
+</note>
+
+
+
+
+ <table frame="all">
+ <title>SSL Configuration</title>
+ <tgroup colsep="1" cols="3">
+ <colspec colname="c1"/>
+ <colspec colname="c2"/>
+ <colspec colname="c3"/>
+ <thead>
+ <row>
+ <entry>Attribute</entry>
+ <entry>Default</entry>
+ <entry>Description</entry>
+ </row>
+ </thead>
+ <tbody>
+ <row>
+ <entry>
+<property>ssl</property>
+ </entry>
+ <entry>
+<option>false</option>
+ </entry>
+ <entry>
+Should connection to proxy use a secure socket layer
+ </entry>
+ </row>
+ <row>
+ <entry>
+<property>sslCiphers</property>
+ </entry>
+ <entry>
+The default JSSE cipher suites
+ </entry>
+ <entry>
+Overrides the cipher suites used to init an SSL socket ignoring any unsupported ciphers
+ </entry>
+ </row>
+ <row>
+ <entry>
+<property>sslProtocol</property>
+ </entry>
+ <entry>
+<varname>TLS</varname>
+ </entry>
+ <entry>
+Overrides the default SSL socket protocol.
+ </entry>
+ </row>
+ <row>
+ <entry>
+<property>sslCertificateEncodingAlgorithm</property>
+ </entry>
+ <entry>
+The default JSSE key manager algorithm
+ </entry>
+ <entry>
+The algorithm of the key manager factory
+ </entry>
+ </row>
+ <row>
+ <entry>
+<property>sslKeyStore</property>
+ </entry>
+ <entry>
+<filename>System.getProperty("user.home") + "/.keystore"</filename>
+ </entry>
+ <entry>
+The location of the key store containing client certificates
+ </entry>
+ </row>
+ <row>
+ <entry>
+<property>sslKeyStorePass</property>
+ </entry>
+ <entry>
+<literal>changeit</literal>
+ </entry>
+ <entry>
+The password granting access to the key store
+ </entry>
+ </row>
+ <row>
+ <entry>
+<property>sslKeyStoreType</property>
+ </entry>
+ <entry>
+<systemitem>JKS</systemitem>
+ </entry>
+ <entry>
+The type of key store.
+ </entry>
+ </row>
+ <row>
+ <entry>
+<property>sslKeyStoreProvider</property>
+ </entry>
+ <entry>
+<systemitem>The default JSSE security provider</systemitem>
+ </entry>
+ <entry>
+The key store provider
+ </entry>
+ </row>
+ <row>
+ <entry>
+<property>sslTrustAlgorithm</property>
+ </entry>
+ <entry>
+The default JSSE trust manager algorithm
+ </entry>
+ <entry>
+The algorithm of the trust manager factory.
+ </entry>
+ </row>
+ <row>
+ <entry>
+<property>sslKeyAlias</property>
+ </entry>
+ <entry>
+
+ </entry>
+ <entry>
+The alias of the key holding the client certificates in the key store
+ </entry>
+ </row>
+ <row>
+ <entry>
+<property>sslCrlFile</property>
+ </entry>
+ <entry>
+
+ </entry>
+ <entry>
+Certificate revocation list
+ </entry>
+ </row>
+ <row>
+ <entry>
+<property>sslTrustMaxCertLength</property>
+ </entry>
+ <entry>
+<literal>5</literal>
+ </entry>
+ <entry>
+The maximum length of a certificate held in the trust store
+ </entry>
+ </row>
+ <row>
+ <entry>
+<property>sslTrustStore</property>
+ </entry>
+ <entry>
+<systemitem>System.getProperty ("javax.net.ssl.trustStorePassword")</systemitem>
+ </entry>
+ <entry>
+The location of the file containing the trust store
+ </entry>
+ </row>
+ <row>
+ <entry>
+<property>sslTrustStorePassword</property>
+ </entry>
+ <entry>
+<varname>System.getProperty ("javax.net.ssl.trustStore")</varname>
+ </entry>
+ <entry>
+The password granting access to the trust store.
+ </entry>
+ </row>
+ <row>
+ <entry>
+<property>sslTrustStoreType</property>
+ </entry>
+ <entry>
+<systemitem>System.getProperty ("javax.net.ssl.trustStoreType")</systemitem>
+ </entry>
+ <entry>
+The trust store type.
+ </entry>
+ </row>
+ <row>
+ <entry>
+<property>sslTrustStoreProvider</property>
+ </entry>
+ <entry>
+<systemitem>System.getProperty ("javax.net.ssl.trustStoreProvider")</systemitem>
+ </entry>
+ <entry>
+The trust store provider.
+ </entry>
+ </row>
+ </tbody>
+ </tgroup>
+ </table>
+
+ <formalpara>
+ <title>HA Configuration
+ </title>
+ <para>Additional configuration properties are used when mod_cluster is configured in clustered mode.
+ </para>
+ </formalpara>
+
+ <table frame="all">
+ <title>HA Configuration</title>
+ <tgroup colsep="1" cols="3">
+ <colspec colname="c1"/>
+ <colspec colname="c2"/>
+ <colspec colname="c3"/>
+ <thead>
+ <row>
+ <entry>Attribute</entry>
+ <entry>Default</entry>
+ <entry>Description</entry>
+ </row>
+ </thead>
+ <tbody>
+ <row>
+ <entry>
+<property>masterPerDomain</property>
+ </entry>
+ <entry>
+<option>false</option>
+ </entry>
+ <entry>
+If the domain directive is used, HA partition should use a singleton master per domain
+ </entry>
+ </row>
+ </tbody>
+ </tgroup>
+ </table>
+
+ <formalpara>
+ <title>Load Configuration
+ </title>
+ <para>Additional configuration properties are used when mod_cluster is configured in JBoss Web standalone or Tomcat.
+ </para>
+ </formalpara>
+
+ <table frame="all">
+ <title>Load Configuration</title>
+ <tgroup colsep="1" cols="3">
+ <colspec colname="c1"/>
+ <colspec colname="c2"/>
+ <colspec colname="c3"/>
+ <thead>
+ <row>
+ <entry>Attribute</entry>
+ <entry>Default</entry>
+ <entry>Description</entry>
+ </row>
+ </thead>
+ <tbody>
+ <row>
+ <entry>
+<property>loadMetricClass</property>
+ </entry>
+ <entry>
+<classname>org.jboss.load.metric. impl.BusyConnectorsLoadMetric</classname>
+ </entry>
+ <entry>
+Class name of an object implementing <filename>org.jboss.load.metric.LoadMetric</filename>
+ </entry>
+ </row>
+ <row>
+ <entry>
+<property>loadMetricCapacity</property>
+ </entry>
+ <entry>
+<option>1</option>
+ </entry>
+ <entry>
+The capacity of the load metric defined via the <property>loadMetricClass</property> property
+ </entry>
+ </row>
+ <row>
+ <entry>
+<property>loadHistory</property>
+ </entry>
+ <entry>
+<literal>9</literal>
+ </entry>
+ <entry>
+The number of historic load values to consider in the load balance factor computation.
+ </entry>
+ </row>
+ <row>
+ <entry>
+<property>loadDecayFactor</property>
+ </entry>
+ <entry>
+<literal>2</literal>
+ </entry>
+ <entry>
+The factor by which historic load values should degrade in significance.
+ </entry>
+ </row>
+ </tbody>
+ </tgroup>
+ </table>
+ </section>
+
+ <section>
+ <title>Server-Side Load Metrics</title>
+ <para>
+ A major feature of mod_cluster is the ability to use server-side load metrics to determine how best to balance requests.
+ </para>
+
+ <para>
+ The <classname>DynamicLoadBalanceFactorProvider</classname> bean computes the load balance factor of a node from a defined set of load metrics.
+ </para>
+
+<programlisting>
+<![CDATA[<bean name="DynamicLoadBalanceFactorProvider" class="org.jboss.modcluster.load.impl.DynamicLoadBalanceFactorProvider" mode="On Demand">
+ <annotation>@org.jboss.aop.microcontainer.aspects.jmx.JMX(name="jboss.web:service=LoadBalanceFactorProvider",exposedInterface=org.jboss.modcluster.load.impl.DynamicLoadBalanceFactorProviderMBean.class)</annotation>
+ <constructor>
+ <parameter>
+ <set elementClass="org.jboss.modcluster.load.metric.LoadMetric">
+ <inject bean="BusyConnectorsLoadMetric"/>
+ <inject bean="HeapMemoryUsageLoadMetric"/>
+ </set>
+ </parameter>
+ </constructor>
+ <property name="history">9</property>
+ <property name="decayFactor">2</property>
+ </bean>
+ ]]>
+</programlisting>
+
+ <para>
+ Load metrics can be configured with an associated weight and capacity:
+ </para>
+ <itemizedlist>
+ <listitem>
+ <para>
+The weight (default is 1) indicates the significance of a metric with respect to the other metrics. For example, a metric of weight 2 will have twice the impact on the overall load factor than a metric of weight 1.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+The capacity of a metric serves 2 functions:
+ </para>
+ <itemizedlist mark='opencircle'>
+ <listitem>
+ <para>
+The weight (default is 1) indicates the significance of a metric with respect to the other metrics. For example, a metric of weight 2 will have twice the impact on the overall load factor than a metric of weight 1.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+The capacity of a metric serves 2 functions:
+ </para>
+ </listitem>
+ </itemizedlist>
+ </listitem>
+ </itemizedlist>
+ <para>
+ Each load metric contributes a value to the overall load factor of a node. The load factors from each metric are aggregated according to their weights.
+ </para>
+ <para>
+ In general, the load factor contribution of given metric is: (load / capacity) * weight / total weight.
+ </para>
+ <para>
+ The <filename>DynamicLoadBalanceFactorProvider</filename> applies a time decay function to the loads returned by each metric. The aggregate load, with respect to previous load values, can be expressed by the following formula:
+ </para>
+
+<programlisting>
+<![CDATA[L = (L0 + L1/D + L2/D2 + L3/D3 + ... + LH/DH) * (1 + D + D2 + D3 + ... DH)
+ ]]>
+</programlisting>
+
+ <para>
+ The aggregate load can be expressed more concisely as by the following formula:
+ </para>
+
+<programlisting>
+<![CDATA[ H H
+ L = ∑ Li/Di * ∑ Di
+ i=0 i=0
+ ]]>
+</programlisting>
+
+ <para>
+ Setting <varname>history = 0</varname> effectively disables the time decay function and only the current load for each metric will be considered in the load balance factor computation.
+ </para>
+ <para>
+ The <varname>mod_cluster proxy</varname> module expects the load factor to be an integer between 0 and 100, where 0 indicates max load and 100 indicates zero load. Therefore, the final load balance factor sent to the proxy = 100 - (L * 100).
+ </para>
+ <para>
+ While you are free to write your own load metrics, the following <varname>LoadMetrics</varname> are available out of the box:
+ </para>
+
+ <formalpara>
+ <title>JBoss Web Metrics
+ </title>
+ <para> The following JBoss Web Metrics are available:
+ </para>
+ </formalpara>
+
+ <itemizedlist>
+ <listitem>
+ <para>
+<varname>ActiveSessionsLoadMetric</varname>
+ </para>
+ <itemizedlist mark='opencircle'>
+ <listitem>
+ <para>
+Requires an explicit capacity
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+Uses <methodname>SessionLoadMetricSource</methodname> to query session managers
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+Analogous to <literal>method=S in mod_jk</literal>
+ </para>
+ </listitem>
+ </itemizedlist>
+ </listitem>
+ </itemizedlist>
+
+<programlisting>
+<![CDATA[<bean name="ActiveSessionsLoadMetric" class="org.jboss.modcluster.load.metric.impl.ActiveSessionsLoadMetric" mode="On Demand">
+ <annotation>@org.jboss.aop.microcontainer.aspects.jmx.JMX(name="jboss.web:service=ActiveSessionsLoadMetric",exposedInterface=org.jboss.modcluster.load.metric.LoadMetricMBean.class)</annotation>
+ <constructor>
+ <parameter><inject bean="SessionLoadMetricSource"/></parameter>
+ </constructor>
+ <property name="capacity">1000</property>
+ </bean>
+ <bean name="SessionLoadMetricSource" class="org.jboss.modcluster.load.metric.impl.SessionLoadMetricSource" mode="On Demand">
+ <constructor>
+ <parameter class="javax.management.MBeanServer"><inject bean="JMXKernel" property="mbeanServer"/></parameter>
+ </constructor>
+ </bean>
+ ]]>
+</programlisting>
+
+ <itemizedlist>
+ <listitem>
+ <para>
+<varname>BusyConnectorsLoadMetric</varname>
+ </para>
+ <itemizedlist mark='opencircle'>
+ <listitem>
+ <para>
+Returns the percentage of connector threads from the thread pool that are busy servicing requests
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+Uses <methodname>ThreadPoolLoadMetricSource</methodname> to query connector thread pools
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+Analogous to method=B in mod_jk
+ </para>
+ </listitem>
+ </itemizedlist>
+ </listitem>
+ </itemizedlist>
+
+<programlisting>
+<![CDATA[<bean name="BusyConnectorsLoadMetric" class="org.jboss.modcluster.load.metric.impl.BusyConnectorsLoadMetric" mode="On Demand">
+ <annotation>@org.jboss.aop.microcontainer.aspects.jmx.JMX(name="jboss.web:service=BusyConnectorsLoadMetric",exposedInterface=org.jboss.modcluster.load.metric.LoadMetricMBean.class)</annotation>
+ <constructor>
+ <parameter><inject bean="ThreadPoolLoadMetricSource"/></parameter>
+ </constructor>
+ </bean>
+ <bean name="ThreadPoolLoadMetricSource" class="org.jboss.modcluster.load.metric.impl.ThreadPoolLoadMetricSource" mode="On Demand">
+ <constructor>
+ <parameter class="javax.management.MBeanServer"><inject bean="JMXKernel" property="mbeanServer"/></parameter>
+ </constructor>
+ </bean>
+ ]]>
+</programlisting>
+
+ <itemizedlist>
+ <listitem>
+ <para>
+<varname>ReceiveTrafficLoadMetric</varname>
+ </para>
+ <itemizedlist mark='opencircle'>
+ <listitem>
+ <para>
+Returns the incoming request traffic in KB/sec
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+Requires an explicit capacity
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+Uses <methodname>RequestProcessorLoadMetricSource</methodname> to query request processors
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+Analogous to method=T in mod_jk
+ </para>
+ </listitem>
+ </itemizedlist>
+ </listitem>
+ </itemizedlist>
+
+<programlisting>
+<![CDATA[ <bean name="RequestCountLoadMetric" class="org.jboss.modcluster.load.metric.impl.RequestCountLoadMetric" mode="On Demand">
+ <annotation>@org.jboss.aop.microcontainer.aspects.jmx.JMX(name="jboss.web:service=RequestCountLoadMetric",exposedInterface=org.jboss.modcluster.load.metric.LoadMetricMBean.class)</annotation>
+ <constructor>
+ <parameter><inject bean="RequestProcessorLoadMetricSource"/></parameter>
+ </constructor>
+ <property name="capacity">1000</property>
+ </bean>
+ <bean name="RequestProcessorLoadMetricSource" class="org.jboss.modcluster.load.metric.impl.RequestProcessorLoadMetricSource" mode="On Demand">
+ <constructor>
+ <parameter class="javax.management.MBeanServer"><inject bean="JMXKernel" property="mbeanServer"/></parameter>
+ </constructor>
+ </bean>
+
+ ]]>
+</programlisting>
+
+ <itemizedlist>
+ <listitem>
+ <para>
+<varname>SendTrafficLoadMetric</varname>
+ </para>
+ <itemizedlist mark='opencircle'>
+ <listitem>
+ <para>
+Returns the outgoing request traffic in KB/sec
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+Requires an explicit capacity
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+Uses <methodname>RequestProcessorLoadMetricSource</methodname> to query request processors
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+Analogous to method=T in mod_jk
+ </para>
+ </listitem>
+ </itemizedlist>
+ </listitem>
+ </itemizedlist>
+
+<programlisting>
+<![CDATA[<bean name="ReceiveTrafficLoadMetric" class="org.jboss.modcluster.load.metric.impl.ReceiveTrafficLoadMetric" mode="On Demand">
+ <annotation>@org.jboss.aop.microcontainer.aspects.jmx.JMX(name="jboss.web:service=ReceiveTrafficLoadMetric",exposedInterface=org.jboss.modcluster.load.metric.LoadMetricMBean.class)</annotation>
+ <constructor>
+ <parameter><inject bean="RequestProcessorLoadMetricSource"/></parameter>
+ </constructor>
+ <property name="capacity">1024</property>
+ </bean>
+ ]]>
+</programlisting>
+
+ <itemizedlist>
+ <listitem>
+ <para>
+<varname>RequestCountLoadMetric</varname>
+ </para>
+ <itemizedlist mark='opencircle'>
+ <listitem>
+ <para>
+Returns the number of requests/sec
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+Requires an explicit capacity
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+Uses <methodname>RequestProcessorLoadMetricSource</methodname> to query request processors
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+Analogous to <literal>method=R</literal> in mod_jk
+ </para>
+ </listitem>
+ </itemizedlist>
+ </listitem>
+ </itemizedlist>
+
+<programlisting>
+<![CDATA[<bean name="SendTrafficLoadMetric" class="org.jboss.modcluster.load.metric.impl.SendTrafficLoadMetric" mode="On Demand">
+ <annotation>@org.jboss.aop.microcontainer.aspects.jmx.JMX(name="jboss.web:service=SendTrafficLoadMetric",exposedInterface=org.jboss.modcluster.load.metric.LoadMetricMBean.class)</annotation>
+ <constructor>
+ <parameter><inject bean="RequestProcessorLoadMetricSource"/></parameter>
+ </constructor>
+ <property name="capacity">512</property>
+ </bean>
+ ]]>
+</programlisting>
+
+ <formalpara>
+ <title>System/JVM Metrics
+ </title>
+ <para> The following System/JVM metrics are available:
+ </para>
+ </formalpara>
+
+ <itemizedlist>
+ <listitem>
+ <para>
+<varname>AverageSystemLoadMetric</varname>
+ </para>
+ <itemizedlist mark='opencircle'>
+ <listitem>
+ <para>
+Returns CPU load
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+Requires Java 1.6+.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+Uses <methodname>OperatingSystemLoadMetricSource</methodname> to generically read attributes
+ </para>
+ </listitem>
+ </itemizedlist>
+ </listitem>
+ </itemizedlist>
+
+<programlisting>
+<![CDATA[<bean name="AverageSystemLoadMetric" class="org.jboss.modcluster.load.metric.impl.AverageSystemLoadMetric" mode="On Demand">
+ <annotation>@org.jboss.aop.microcontainer.aspects.jmx.JMX(name="jboss.web:service=AverageSystemLoadMetric",exposedInterface=org.jboss.modcluster.load.metric.LoadMetricMBean.class)</annotation>
+ <constructor>
+ <parameter><inject bean="OperatingSystemLoadMetricSource"/></parameter>
+ </constructor>
+ </bean>
+ <bean name="OperatingSystemLoadMetricSource" class="org.jboss.modcluster.load.metric.impl.OperatingSystemLoadMetricSource" mode="On Demand">
+ </bean>
+ ]]>
+</programlisting>
+
+ <itemizedlist>
+ <listitem>
+ <para>
+<varname>SystemMemoryUsageLoadMetric</varname>
+ </para>
+ <itemizedlist mark='opencircle'>
+ <listitem>
+ <para>
+Returns system memory usage
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+Requires <classname>com.sun.management.OperatingSystemMXBean</classname> (available in Sun's JDK or OpenJDK)
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+Uses <methodname>OperatingSystemLoadMetricSource</methodname> to generically read attributes
+ </para>
+ </listitem>
+ </itemizedlist>
+ </listitem>
+ </itemizedlist>
+
+<programlisting>
+<![CDATA[<bean name="SystemMemoryUsageLoadMetric" class="org.jboss.modcluster.load.metric.impl.SystemMemoryUsageLoadMetric" mode="On Demand">
+ <annotation>@org.jboss.aop.microcontainer.aspects.jmx.JMX(name="jboss.web:service=SystemMemoryUsageLoadMetric",exposedInterface=org.jboss.modcluster.load.metric.LoadMetricMBean.class)</annotation>
+ <constructor>
+ <parameter><inject bean="OperatingSystemLoadMetricSource"/></parameter>
+ </constructor>
+ </bean>
+ ]]>
+</programlisting>
+
+ <itemizedlist>
+ <listitem>
+ <para>
+<varname>HeapMemoryUsageLoadMetric</varname>
+ </para>
+ <itemizedlist mark='opencircle'>
+ <listitem>
+ <para>
+Returns the heap memory usage as a percentage of max heap size
+ </para>
+ </listitem>
+ </itemizedlist>
+ </listitem>
+ </itemizedlist>
+
+<programlisting>
+<![CDATA[<bean name="HeapMemoryUsageLoadMetric" class="org.jboss.modcluster.load.metric.impl.HeapMemoryUsageLoadMetric" mode="On Demand">
+ <annotation>@org.jboss.aop.microcontainer.aspects.jmx.JMX(name="jboss.web:service=HeapMemoryUsageLoadMetric",exposedInterface=org.jboss.modcluster.load.metric.LoadMetricMBean.class)</annotation>
+ </bean>
+ ]]>
+</programlisting>
+
+ <formalpara>
+ <title>Other metrics
+ </title>
+ <para> Other metrics are available as follows:
+ </para>
+ </formalpara>
+
+ <itemizedlist>
+ <listitem>
+ <para>
+<varname>ConnectionPoolUsageLoadMetric</varname>
+ </para>
+ <itemizedlist mark='opencircle'>
+ <listitem>
+ <para>
+Requires an explicit capacity
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+Returns the percentage of connections from a connection pool that are in use.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+Uses <methodname>ConnectionPoolLoadMetricSource</methodname> to query JCA connection pools
+ </para>
+ </listitem>
+ </itemizedlist>
+ </listitem>
+ </itemizedlist>
+
+<programlisting>
+<![CDATA[ <bean name="ConnectionPoolUsageMetric" class="org.jboss.modcluster.load.metric.impl.ConnectionPoolUsageLoadMetric" mode="On Demand">
+ <annotation>@org.jboss.aop.microcontainer.aspects.jmx.JMX(name="jboss.web:service=ConnectionPoolUsageLoadMetric",exposedInterface=org.jboss.modcluster.load.metric.LoadMetricMBean.class)</annotation>
+ <constructor>
+ <parameter><inject bean="ConnectionPoolLoadMetricSource"/></parameter>
+ </constructor>
+ </bean>
+ <bean name="ConnectionPoolLoadMetricSource" class="org.jboss.modcluster.load.metric.impl.ConnectionPoolLoadMetricSource" mode="On Demand">
+ <constructor>
+ <parameter class="javax.management.MBeanServer"><inject bean="JMXKernel" property="mbeanServer"/></parameter>
+ </constructor>
+ </bean>
+ ]]>
+</programlisting>
+
+
+ </section>
+
+
+
</chapter>
Modified: projects/docs/enterprise/5.0/mod_cluster/en-US/MigratingFromModJK.xml
===================================================================
--- projects/docs/enterprise/5.0/mod_cluster/en-US/MigratingFromModJK.xml 2010-01-07 04:54:46 UTC (rev 99090)
+++ projects/docs/enterprise/5.0/mod_cluster/en-US/MigratingFromModJK.xml 2010-01-07 05:24:02 UTC (rev 99091)
@@ -12,7 +12,7 @@
The migration from <application>mod_jk</application> to mod_cluster is not very complex. There are only a few worker properties that cannot be mapped to mod_cluster parameters.
</para>
<para>
- The table of worker properties and how to transfer them to the <classname>ClusterListener</classname> parameters follows:
+ The table of worker properties and how to transfer them to the <classname>mod_cluster configuration</classname> parameters follows:
</para>
<table frame="all" id="tabl-mod_cluster-Migration_from_mod_jk_to_mod_cluster-Worker_Property_Transfer">
<title>Worker Property Transfer</title>
@@ -26,7 +26,7 @@
mod_jk worker property
</entry>
<entry>
- <classname>ClusterListener</classname> Parameter
+ <classname>mod_cluster configuration</classname> Parameter
</entry>
<entry>
Remarks
Modified: projects/docs/enterprise/5.0/mod_cluster/en-US/Overview.xml
===================================================================
--- projects/docs/enterprise/5.0/mod_cluster/en-US/Overview.xml 2010-01-07 04:54:46 UTC (rev 99090)
+++ projects/docs/enterprise/5.0/mod_cluster/en-US/Overview.xml 2010-01-07 05:24:02 UTC (rev 99091)
@@ -5,7 +5,7 @@
<title>Overview</title>
<!-- <para>This is a test paragraph</para> -->
<section id="sect-mod_cluster-Overview-Introducton">
- <title>Introducton</title>
+ <title>Introduction</title>
<para>
<classname>JBoss mod_cluster</classname> is an httpd-based load balancer. Like <application>mod_jk</application> and <application>mod_proxy</application>, mod_cluster uses a communication channel to forward requests from httpd to one of a set of application server nodes.
</para>
@@ -21,24 +21,19 @@
<itemizedlist>
<listitem>
<para>
- <application>Linux x86, x64, ia64</application>
+ <application>RHEL4.5 x86, x64</application>
</para>
</listitem>
<listitem>
<para>
- <application>Solaris x86, SPARC</application>
+ <application>Solaris x86, x64</application>
</para>
</listitem>
<listitem>
<para>
- <application>Windows x86, x64, ia64</application>
+ <application>Windows x86, x64</application>
</para>
</listitem>
- <listitem>
- <para>
- <application>HP-UX PA-RISC, ia64</application>
- </para>
- </listitem>
</itemizedlist>
</section>
@@ -90,11 +85,11 @@
</para>
</listitem>
</itemizedlist>
- <note>
+<!-- <note>
<para>
Note: httpd-2.2.8+ is already in the bundles, so if you use the bundle you don't need to download <application>Apache</application> httpd.
</para>
- </note>
+ </note> -->
</section>
<section id="sect-mod_cluster-Overview-Configuration">
@@ -107,7 +102,7 @@
<section id="sect-mod_cluster-Overview-Migration_from_mod_jk">
<title>Migration from mod_jk</title>
<para>
- In general, much of the configuration previously found in <filename>httpd.conf</filename> is now defined in the application server nodes. Refer to the relavant chapter in this publication.
+ In general, much of the configuration previously found in <filename>httpd.conf</filename> is now defined in the application server nodes. Refer to the relevant chapter in this publication.
</para>
</section>
@@ -123,7 +118,7 @@
<para>
The mod_cluster install currently has the following limitations:
</para>
- <itemizedlist>
+<!-- <itemizedlist>
<listitem>
<para>
Dynamic load balance factor calculation support is currently limited to the JBoss AS integration.
@@ -133,7 +128,8 @@
<para>
Clustered-mode support is currently limited to the JBoss AS integration
</para>
- </listitem>
+ </listitem> -->
+ <itemizedlist>
<listitem>
<para>
Checksum verification of proxy advertisements (if advertise is enabled) will never fail.
Modified: projects/docs/enterprise/5.0/mod_cluster/en-US/QuickStartGuide.xml
===================================================================
--- projects/docs/enterprise/5.0/mod_cluster/en-US/QuickStartGuide.xml 2010-01-07 04:54:46 UTC (rev 99090)
+++ projects/docs/enterprise/5.0/mod_cluster/en-US/QuickStartGuide.xml 2010-01-07 05:24:02 UTC (rev 99091)
@@ -18,8 +18,8 @@
<section id="sect-mod_cluster-Quick_Start_Guide-Install_the_httpd_binary">
<title>Install the httpd binary</title>
- <formalpara id="form-mod_cluster-Install_the_httpd_binary-Install_the_entire_httpd">
- <title>Install the entire httpd</title>
+<!-- <formalpara id="form-mod_cluster-Install_the_httpd_binary-Install_the_entire_httpd">
+ <title>Install the httpd bundles</title>
<para>
The httpd-side bundles are <application>gzipped tars</application> and include a full httpd install. As they already contain an <application>Apache httpd</application> install, you do not need to download Apache httpd. Extract them in root, e.g.
</para>
@@ -31,11 +31,11 @@
</programlisting>
<para>
That will provide you with a full httpd install in the <filename>/opt/jboss directory</filename>.
- </para>
+ </para> -->
<formalpara id="form-mod_cluster-Install_the_httpd_binary-Install_only_the_modules">
<title>Install only the modules</title>
<para>
- If you already have a working httpd install that you would prefer to use, you'll need to download the bundle named <package>mod_cluster httpd dynamic libraries</package> corresponding to your platform. Extract the modules and copy them directly to the module directory of your httpd install.
+ To supplement the working httpd install currently in use, download the module bundle named <package>mod_cluster httpd dynamic libraries</package> corresponding to your platform. Extract the modules and copy them directly to the module directory of the httpd install.
</para>
</formalpara>
@@ -47,7 +47,7 @@
Then copy the following files to the module directory.
</para>
<itemizedlist>
- <listitem>
+<!-- <listitem>
<para>
<filename>mod_proxy.so</filename>
</para>
@@ -56,7 +56,7 @@
<para>
<filename>mod_proxy_ajp.so</filename>
</para>
- </listitem>
+ </listitem> -->
<listitem>
<para>
<filename>mod_slotmem.so</filename>
@@ -82,8 +82,8 @@
<section id="sect-mod_cluster-Quick_Start_Guide-Configure_httpd">
<title>Configure httpd</title>
- <para>
- Add the following to <filename>httpd.conf</filename>. If you have extracted the download bundle to root, as shown above, and are using that extract as your httpd install, <filename>httpd.conf</filename> is located in <filename>opt/jboss/httpd/httpd/conf/</filename>.
+<!-- <para>
+ Add the following to <filename>httpd.conf</filename>. If you have extracted the download bundle to root, as shown above, and are using that extract as your httpd install, <filename>httpd.conf</filename> is located in <filename>opt/jboss/httpd/httpd/conf/</filename>.
</para>
<programlisting>
@@ -110,14 +110,16 @@
AdvertiseFrequency 5
</VirtualHost>
-</programlisting>
+</programlisting> -->
+<!-- <para>
+ If you are using your own install of httpd, <filename>httpd.conf</filename> is found in the install <filename>conf</filename> directory. The content to add to <filename>httpd.conf</filename> is slightly different from the above (different path to the various <filename>.so</filename> files):
+ </para> -->
<para>
- If you are using your own install of httpd, <filename>httpd.conf</filename> is found in the install <filename>conf</filename> directory. The content to add to <filename>httpd.conf</filename> is slightly different from the above (different path to the various <filename>.so</filename> files):
- </para>
-
+ With the existing install of httpd on your system, <filename>httpd.conf</filename> is found in the install <filename>conf</filename> directory. Add the following to <filename>httpd.conf</filename>:
+ </para>
<programlisting>
-LoadModule proxy_module modules/mod_proxy.so
-LoadModule proxy_ajp_module modules/mod_proxy_ajp.so
+<!-- LoadModule proxy_module modules/mod_proxy.so
+LoadModule proxy_ajp_module modules/mod_proxy_ajp.so -->
LoadModule slotmem_module modules/mod_slotmem.so
LoadModule manager_module modules/mod_manager.so
LoadModule proxy_cluster_module modules/mod_proxy_cluster.so
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-01-07 04:54:46 UTC (rev 99090)
+++ projects/docs/enterprise/5.0/mod_cluster/en-US/Revision_History.xml 2010-01-07 05:24:02 UTC (rev 99091)
@@ -7,7 +7,7 @@
<revhistory>
<revision>
<revnumber>1.0</revnumber>
- <date>Wed Dec 09 2009</date>
+ <date>Thursday Jan 07 2010</date>
<author>
<firstname>Gary</firstname>
<surname>Meintjes</surname>
More information about the jboss-cvs-commits
mailing list