Author: rjung
Date: Tue Sep 1 14:29:16 2015
New Revision: 1700574
URL: http://svn.apache.org/r1700574
Log:
More minor docs improvements.
Modified:
tomcat/jk/trunk/xdocs/common_howto/loadbalancers.xml
tomcat/jk/trunk/xdocs/common_howto/proxy.xml
tomcat/jk/trunk/xdocs/common_howto/quick.xml
tomcat/jk/trunk/xdocs/common_howto/timeouts.xml
tomcat/jk/trunk/xdocs/common_howto/workers.xml
Modified: tomcat/jk/trunk/xdocs/common_howto/loadbalancers.xml
URL:
http://svn.apache.org/viewvc/tomcat/jk/trunk/xdocs/common_howto/loadbalancers.xml?rev=1700574&r1=1700573&r2=1700574&view=diff
==============================================================================
--- tomcat/jk/trunk/xdocs/common_howto/loadbalancers.xml (original)
+++ tomcat/jk/trunk/xdocs/common_howto/loadbalancers.xml Tue Sep 1 14:29:16
2015
@@ -40,7 +40,7 @@ This management includes:
Instantiating the workers in the web server.
</li>
<li>
-Using the worker's load-balancing factor, perform weighted load balancing
+Using the worker's load balancing factor, perform weighted load balancing
(distributing load according to defined strengths of the targets).
</li>
<li>
@@ -49,19 +49,19 @@ Keeping requests belonging to the same s
</li>
<li>
Identifying failed Tomcat workers, suspending requests to them and instead
-falling-back on other workers managed by the load balancer.
+failing over on other workers managed by the load balancer.
</li>
<li>
Providing status and load metrics for the load balancer itself and all
members via the status worker interface.
</li>
<li>
-Allowing to dynamically reconfigure load-balancing via the status worker
+Allowing to dynamically reconfigure load balancing via the status worker
interface.
</li>
</ul>
<p>
-Workers managed by the same load balancer worker are load-balanced
+Workers managed by the same load balancer worker are load balanced
(based on their configured balancing factors and current request or session
load)
and also secured against failure by providing failover to other members of the
same
load balancer. So a single Tomcat process death will not "kill" the entire
site.
@@ -212,7 +212,7 @@ especially useful when combined with loa
worker.jkstatus.type=status
</source>
<p>Next thing is to mount the requests to the jkstatus worker. For Apache
-web servers use the:</p>
+HTTP Servers use:</p>
<source>
# Add the jkstatus mount point
JkMount /jkmanager/* jkstatus
Modified: tomcat/jk/trunk/xdocs/common_howto/proxy.xml
URL:
http://svn.apache.org/viewvc/tomcat/jk/trunk/xdocs/common_howto/proxy.xml?rev=1700574&r1=1700573&r2=1700574&view=diff
==============================================================================
--- tomcat/jk/trunk/xdocs/common_howto/proxy.xml (original)
+++ tomcat/jk/trunk/xdocs/common_howto/proxy.xml Tue Sep 1 14:29:16 2015
@@ -29,8 +29,9 @@
<body>
<section name="Introduction">
<br/>
-<p>The Apache module mod_jk and its ISAPI and NSAPI variants connect
-a web server to a backend (typically Tomcat) using the AJP protocol.
+<p>The Apache HTTP Server module mod_jk and its ISAPI and NSAPI redirector
+variants for Microsoft IIS and the iPlanet Web Server connect
+the web server to a backend (typically Tomcat) using the AJP protocol.
The web server receives an HTTP(S) request and the module forwards
the request to the backend. This function is usually called a gateway
or a proxy, in the context of HTTP it is called a reverse proxy.
@@ -67,9 +68,9 @@ This is also equal to <code>getServerNam
is contained in the request. In this case the server name is taken from that
header.
</li>
<li>local IP address: <code>getLocalAddr()</code>.
-The local IP address was initially not supported. It is available when using
mod_jk 1.2.41
-with Apache or IIS (not for the NSAPI plugin) together with Tomcat version at
least
-6.0.42, 7.0.55 or 8.0.11. For older versions, <code>getLocalAddr()</code>
+The local IP address was initially not supported. It is available when using
version 1.2.41
+for Apache or IIS together with Tomcat version at least
+6.0.42, 7.0.55 or 8.0.11. For older versions or when using the NSAPI
redirector, <code>getLocalAddr()</code>
will incorrectly return the same result as <code>getLocalName()</code>.
As a workaround you can forward the local IP address by setting
<code>JkEnvVar SERVER_ADDR</code> and then either using
@@ -85,9 +86,9 @@ if it contains an explicit port, or is e
<li>client address: <code>getRemoteAddr()</code>
</li>
<li>client port: <code>getRemotePort()</code>.
-The remote port was initially not supported. It is available when using mod_jk
1.2.32
-with Apache or IIS (not for the NSAPI plugin) together with Tomcat version at
least
-5.5.28, 6.0.20 or 7.0.0. For older versions, <code>getRemotePort()</code>
+The remote port was initially not supported. It is available when using
version 1.2.32
+for Apache or IIS together with Tomcat version at least
+5.5.28, 6.0.20 or 7.0.0. For older versions or when using the NSAPI
redirector, <code>getRemotePort()</code>
will incorrectly return 0 or -1. As a workaround you can forward the remote
port by setting
<code>JkEnvVar REMOTE_PORT</code> and then either using
<code>request.getAttribute("REMOTE_PORT")</code> instead of
<code>getRemotePort()</code>
@@ -112,7 +113,7 @@ if <code>tomcatAuthentication="false"</c
<li>query string: <code>getQueryString()</code>
</li>
</ul>
-The following additional SSL-related data will be made available by Apache and
forwarded by mod_jk only
+The following additional SSL-related data will be made available by the Apache
HTTP Server and forwarded by mod_jk only
if you set <code>SSLOptions +StdEnvVars</code>. For the certificate
information you also need
to set <code>SSLOptions +ExportCertData</code>.
<ul>
@@ -151,10 +152,10 @@ more cascading reverse proxies in front)
content of such a header as the client IP address to pass to the backend.
</p>
<p>So we might need to manipulate some of the data that AJP sends to the
backend.
-When using mod_jk inside Apache httpd you can use several httpd environment
+When using mod_jk inside the Apache HTTP Server you can use several Apache
environment
variables to let mod_jk know, which data it should forward. These environment
variables
-can be set by the httpd directives SetEnv or SetEnvIf, but also in a very
flexible
-way using mod_rewrite (since httpd 2.x it can not only test against environment
+can be set by the configuration directives SetEnv or SetEnvIf, but also in a
very flexible
+way using mod_rewrite (since Apache 2.x it can not only test against
environment
variables, but also set them).
</p>
<p>The following list contains all environment variables mod_jk checks, before
@@ -192,7 +193,7 @@ from the web server. Only in case you wa
using these variables.
</p>
<p>Some of these variables might also be used by other web server modules. All
-variables whose name does not begin with "JK" are set directly by Apache httpd.
+variables whose name does not begin with "JK" are set directly by the Apache
HTTP Server.
If you want to change the data, but do not want to negatively influence the
behaviour
of other modules, you can change the names of all variables mod_jk uses to
private ones.
For the details see the <a href="../reference/apache.html">Apache
reference</a> page.
@@ -202,7 +203,7 @@ For the details see the <a href="../refe
<p>In addition there are two special shortcuts to influence the client IP
address that is forwarded.
Using <code>JkOptions ForwardLocalAddress</code> you can forward the local IP
address of the web server
as the client IP address. This can be useful, e.g. when using the Tomcat
remote address valve for
-allowing connections only from registered Apache web servers.
+allowing connections only from registered Apache HTTP Servers.
Using <code>JkOptions ForwardPhysicalAddress</code> you always forward the
physical peer
IP address as the client address. By default mod_jk
uses the logical address as provided by the web server. For example the module
@@ -213,9 +214,9 @@ in the <code>X-Forwarded-For</code> head
<section name="Tomcat AJP Connector Settings">
<br/>
<p>As an alternative to using the environment variables described in the
previous section
-(which do only exist when using Apache httpd), you can also configure Tomcat
to overwrite
+(which do only exist when using Apache), you can also configure Tomcat to
overwrite
some of the communications data forwarded by mod_jk. The AJP connector in
Tomcat's <code>server.xml</code>
-allows to set the <a
href="http://tomcat.apache.org/tomcat-6.0-doc/config/ajp.html#Attributes";>following
properties</a>:
+allows to set the <a
href="http://tomcat.apache.org/tomcat-8.0-doc/config/ajp.html#Attributes";>following
properties</a>:
<ul>
<li>proxyName: server name as returned by <code>getServerName()</code>
</li>
@@ -248,7 +249,7 @@ here are the steps.
<p>Case A: You need to make the application available at a simple URL, but it
is OK, if
users proceed using the more complex URLs, as long as they don't have to type
them in.
That's the easy case, and if this suffices to you, you're lucky. Use a simply
RedirectMatch
-for Apache httpd:
+for the Apache HTTP Server:
</p>
<source>
RedirectMatch ^/$ http://www.mycompany.com/myapp/
@@ -260,7 +261,7 @@ and each visitor will be immediately red
<p>Case B: You need to hide path components for all requests going to the
application.
Here's the recipe for the case, where you want to hide the first path component
<code>/myapp</code>. More complex manipulations are left as an exercise to the
reader.
-First the solution for the case of Apache httpd:
+First the solution for the case of the Apache HTTP Server:
</p>
<p>1. Use <a
href="http://httpd.apache.org/docs/current/mod/mod_rewrite.html";><code>mod_rewrite</code></a>
to add <code>/myapp</code> to all requests before forwarding to the backend:
@@ -296,12 +297,12 @@ In this case check, whether you find a c
to configure the base URL. If not, your only chance is to parse all response
content bodies and do search and replace. This is fragile and very resource
intensive.
If you really need to do this, you can use
-<a
href="http://apache.webthing.com/mod_proxy_html/";><code>mod_proxy_html</code></a>,
+<a
href="http://httpd.apache.org/docs/current/mod/mod_proxy_html.html";><code>mod_proxy_html</code></a>,
<a
href="http://httpd.apache.org/docs/current/mod/mod_substitute.html";><code>mod_substitute</code></a>
or <a
href="http://blogs.sun.com/basant/entry/using_mod_sed_to_filter";><code>mod_sed</code></a>
for this task.
</p>
-<p>If you are using Microsoft IIS as a web server, the ISAPI plugin provides a
way
+<p>If you are using Microsoft IIS as a web server, the ISAPI redirector
provides a way
of doing the first step with a builtin feature. You define a mapping file for
simple prefix
changes like this:
</p>
@@ -341,10 +342,10 @@ the one which was used for the original
<p>
For historical reasons, there have been several alternatives, how mod_jk and
the ISAPI
plugin encoded the resulting URL before sending it to the backend. They could
be chosen via
-<code>JkOptions</code> (Apache httpd) or <code>uri_select</code> (ISAPI). None
of those historical
+<code>JkOptions</code> (mod_jk) or <code>uri_select</code> (ISAPI). None of
those historical
encodings are recommended, because they have either negative functionality
implications or
pose a security risk. The default encoding since version 1.2.24 is
<code>ForwardURIProxy</code>
-(Apache httpd) or <code>proxy</code> (ISAPI) and it is strongly recommended to
keep the default
+(mod_jk) or <code>proxy</code> (ISAPI) and it is strongly recommended to keep
the default
and remove all old explicit settings.
</p>
</subsection>
@@ -352,11 +353,11 @@ and remove all old explicit settings.
<section name="Request Attributes">
<br/>
<p>
-You can also add more attributes to any request you are forwarding when using
Apache httpd.
+You can also add more attributes to any request you are forwarding when using
the Apache HTTP Server.
For this use the <code>JkEnvVar</code> directive (for details see the
<a href="../reference/apache.html">Apache reference</a> page). Such request
attributes can be
retrieved on the Tomcat side via request.getAttribute(attributeName).
-Note that their names will not be listed in request.getAttributeNames()!
+Note that the names of attributes set via mod_jk will not be listed in
request.getAttributeNames()!
</p>
</section>
</body>
Modified: tomcat/jk/trunk/xdocs/common_howto/quick.xml
URL:
http://svn.apache.org/viewvc/tomcat/jk/trunk/xdocs/common_howto/quick.xml?rev=1700574&r1=1700573&r2=1700574&view=diff
==============================================================================
--- tomcat/jk/trunk/xdocs/common_howto/quick.xml (original)
+++ tomcat/jk/trunk/xdocs/common_howto/quick.xml Tue Sep 1 14:29:16 2015
@@ -30,14 +30,15 @@
<section name="Introduction">
<p>
This document describes the configuration files used by JK on the
- Web Server side for the 'impatient':
+ web server side for the 'impatient':
<ul>
<li>
- <b>workers.properties</b> is a mandatory file used by the webserver and
which
- is the same for all JK implementations (Apache/IIS/NES).
+ <b>workers.properties</b> is a mandatory file used by the web server and
which
+ is the same for all JK implementations (mod_jk for the Apache HTTP Server,
+ ISAPI for Microsoft IIS, NSAPI for the iPlanet Web Server).
</li>
<li>
- <b>web server</b> add-ons to be set on the webserver side.
+ <b>web server</b> add-ons to be set on the web server side.
</li>
</ul>
</p>
@@ -49,7 +50,7 @@
<section name="Minimum workers.properties">
<p>
- Here is a minimum <b>workers.properties</b>, using just ajp13 to connect
your Apache webserver
+ Here is a minimum <b>workers.properties</b>, using just ajp13 to connect
your web server
to the Tomcat engine, complete documentation is available in <a
href="workers.html">Workers HowTo</a>.
</p>
<p>
@@ -66,10 +67,10 @@
</p>
</section>
-<section name="Minimum Apache web server configuration">
+<section name="Minimum Apache HTTP Server configuration">
<p>
- Here is a minimum information about Apache configuration, a
- more complete <a href="../webserver_howto/apache.html">separate HowTo for
Apache</a> is available.
+ Here is some very basic information about Apache configuration, a
+ more complete <a href="../webserver_howto/apache.html">HowTo for Apache</a>
is available.
</p>
<p>
You should first have <b>mod_jk.so</b> (unix) or <b>mod_jk.dll</b> (Windows)
installed
@@ -81,10 +82,11 @@
<li>/usr/lib/apache/</li>
<li>/usr/lib/apache2/</li>
<li>/usr/local/apache/libexec/</li>
+ <li>/usr/local/apache/modules/</li>
</ul>
</p>
<p>
- Usual locations for modules directory on Windows :
+ Usual locations for modules directory on Windows:
<ul>
<li>C:\Program Files\Apache Group\Apache\modules\</li>
<li>C:\Program Files\Apache Group\Apache2\modules\</li>
@@ -107,7 +109,7 @@
</ul>
</p>
<p>
- Usual locations for configuration directory on Windows :
+ Usual locations for configuration directory on Windows:
<ul>
<li>C:\Program Files\Apache Group\Apache\conf\</li>
<li>C:\Program Files\Apache Group\Apache2\conf\</li>
@@ -118,8 +120,8 @@
# Load mod_jk module
# Update this path to match your modules location
- LoadModule jk_module libexec/mod_jk.so
- # Declare the module for <IfModule directive> (remove this line on
Apache 2.x)
+ LoadModule jk_module modules/mod_jk.so
+ # Declare the module for <IfModule directive> (remove this line for
Apache 2.x)
AddModule mod_jk.c
# Where to find workers.properties
# Update this path to match your conf directory location (put
workers.properties next to httpd.conf)
@@ -141,18 +143,18 @@
</p>
</section>
-<section name="Minimum IIS web server configuration">
+<section name="Minimum Microsoft IIS configuration">
<p>
- A separate <a href="../webserver_howto/iis.html">HowTo for the IIS web
server</a> is available.
+ A separate <a href="../webserver_howto/iis.html">HowTo for the Microsoft IIS
web server</a> is available.
</p>
<todo>
More information to be added!
</todo>
</section>
-<section name="Minimum NES/iPlanet/Sun web server configuration">
+<section name="Minimum iPlanet Web Server configuration">
<p>
- A separate <a href="../webserver_howto/nes.html">HowTo for the
Netscape/iPlanet/Sun web server</a> is available.
+ A separate <a href="../webserver_howto/nes.html">HowTo for the iPlanet Web
Server</a> is available.
<todo>
More information to be added?
</todo>
Modified: tomcat/jk/trunk/xdocs/common_howto/timeouts.xml
URL:
http://svn.apache.org/viewvc/tomcat/jk/trunk/xdocs/common_howto/timeouts.xml?rev=1700574&r1=1700573&r2=1700574&view=diff
==============================================================================
--- tomcat/jk/trunk/xdocs/common_howto/timeouts.xml (original)
+++ tomcat/jk/trunk/xdocs/common_howto/timeouts.xml Tue Sep 1 14:29:16 2015
@@ -216,17 +216,17 @@ Until version 1.2.26, the maintenance ta
processed. So if your web server has processes that do not receive any
requests for a long time, there is no way to close the idle connections
in its pool. Starting with version 1.2.27 you can configure an independent
-watchdog thread when using Apache 2.x with threaded APR or IIS.
+watchdog thread when using Apache HTTP Server 2.x with threaded APR or
Microsoft IIS.
</p>
<p>
The maximum connection pool size can be configured with the
attribute <b>connection_pool_size</b>. We generally do not recommend
-to use this attribute in combination with Apache httpd. For
-Apache httpd we automatically detect the number of threads per
-process and set the maximum pool size to this value. For IIS we use
+to use this attribute in combination with Apache HTTP Server. For
+Apache we automatically detect the number of threads per
+process and set the maximum pool size to this value. For Microsoft IIS we use
a default value of 250 (before version 1.2.20: 10),
-for the Sun Web Server the default is "1".
-We strongly recommend adjusting this value for IIS and the Sun Web Server
+for the iPlanet Web Server the default is "1".
+We strongly recommend adjusting this value for IIS and the iPlanet Web Server
to the number of requests one web server process should
be able to send to a backend in parallel. You should measure how many
connections
you need during peak hours without performance problems, and then add some
@@ -278,8 +278,8 @@ on good configuration values for the fir
<p>
In case none of our recommendations help and you are definitively having
problems with idle connection drops, you can disable the use of persistent
-connections when using JK together with Apache httpd. For this you set
-"JkOptions +DisableReuse" in your Apache httpd configuration.
+connections when using JK together with Apache HTTP Server. For this you set
+"JkOptions +DisableReuse" in your Apache configuration.
The amount of performance impact this will have depends on the details of
your network and your firewall.
</p>
@@ -314,8 +314,8 @@ The default value is "0" (timeout disabl
millisecond value.
</p>
<p>
-In combination with Apache httpd, you can also set a more flexible
reply_timeout
-using an httpd environment variable. If you set the variable JK_REPLY_TIMEOUT
+In combination with Apache HTTP Server, you can also set a more flexible
reply_timeout
+using an Apache environment variable. If you set the variable JK_REPLY_TIMEOUT
to some integer value, this value will be used instead of the value in
the worker configuration. This way you can set reply timeouts more flexible
with mod_setenvif and mod_rewrite depending on URI, query string etc.
Modified: tomcat/jk/trunk/xdocs/common_howto/workers.xml
URL:
http://svn.apache.org/viewvc/tomcat/jk/trunk/xdocs/common_howto/workers.xml?rev=1700574&r1=1700573&r2=1700574&view=diff
==============================================================================
--- tomcat/jk/trunk/xdocs/common_howto/workers.xml (original)
+++ tomcat/jk/trunk/xdocs/common_howto/workers.xml Tue Sep 1 14:29:16 2015
@@ -32,7 +32,7 @@
<section name="Introduction">
<p>
A Tomcat worker is a Tomcat instance that is waiting to execute servlets on
behalf of some web server.
-For example, we can have a web server such as Apache forwarding servlet
requests to a
+For example, we can have a web server such as the Apache HTTP Server
forwarding servlet requests to a
Tomcat process (the worker) running behind it.
</p>
<p>
@@ -92,7 +92,7 @@ When starting up, the web server plugin
<b>worker.list</b> property, these are also the workers to whom you can map
requests. The directive can be used multiple times.
</p>
-<subsection name="Workers Type">
+<subsection name="Worker Types">
<p>
Each named worker should also have a few entries to provide additional
information on his behalf.
This information includes the worker's type and other related worker
information.
@@ -101,10 +101,11 @@ Currently the following worker types tha
<table>
<tr><th>Type</th><th>Description</th></tr>
- <tr><td>ajp12</td><td>This worker knows how to forward requests to
out-of-process Tomcat workers using the ajpv12 protocol.</td></tr>
- <tr><td>ajp13</td><td>This worker knows how to forward requests to
out-of-process Tomcat workers using the ajpv13 protocol.</td></tr>
- <tr><td>lb</td><td>This is a load-balancing worker; it knows how to provide
round-robin based sticky load balancing with a certain level of
fault-tolerance.</td></tr>
+ <tr><td>ajp13</td><td>This worker knows how to forward requests to
out-of-process Tomcat workers using the ajp13 protocol.</td></tr>
+ <tr><td>lb</td><td>This is a load balancing worker; it knows how to provide
flexible load balancing with a certain level of fault-tolerance.</td></tr>
<tr><td>status</td><td>This is a status worker for managing load
balancers.</td></tr>
+ <tr><td>ajp12</td><td>This worker knows how to forward requests to
out-of-process Tomcat workers using the ajp12 protocol. It is
deprecated</td></tr>
+ <tr><td>ajp14</td><td>This worker knows how to forward requests to
out-of-process Tomcat workers using the ajp14 protocol. It is
experimental</td></tr>
</table>
<p>
@@ -118,9 +119,9 @@ in the table (a worker name may only con
</p>
<source>
- # Defines a worker named "local" that uses the ajpv12 protocol to forward
requests to a Tomcat process.
+ # Defines a worker named "local" that uses the ajp12 protocol to forward
requests to a Tomcat process.
worker.local.type=ajp12
- # Defines a worker named "remote" that uses the ajpv13 protocol to forward
requests to a Tomcat process.
+ # Defines a worker named "remote" that uses the ajp13 protocol to forward
requests to a Tomcat process.
worker.remote.type=ajp13
# Defines a worker named "loadbalancer" that loadbalances several Tomcat
processes transparently.
worker.loadbalancer.type=lb
@@ -142,18 +143,18 @@ worker.<worker name>.<property&
Each worker has a set of properties that you can set as specified in the
following subsections:
-<subsection name="ajp12 Worker properties">
+<subsection name="ajp12 Worker Properties">
<p><warn>
-The <b>ajp12</b> has been <b>deprecated</b> with Tomcat 3.3.x and you should
use instead
-<b>ajp13</b> which is the only ajp protocol known by all Tomcat 4 and above.
+The worker type <b>ajp12</b> has been <b>deprecated</b> and you should use
instead
+<b>ajp13</b> instead.
</warn></p>
<p>
The ajp12 typed workers forward requests to out-of-process Tomcat workers
-using the ajpv12 protocol over TCP/IP sockets.
+using the ajp12 protocol over TCP/IP sockets. It does not use persistent
connections.
</p>
<p>
-the ajp12 worker properties are :
+The ajp12 worker properties are:
</p>
<p>
@@ -165,39 +166,39 @@ the ajp12 worker properties are :
</p>
<p>
-<b>lbfactor</b> property is used when working with a load balancer worker,
this is the load-balancing factor for the worker.
-We'll see more on this in the <a href="../common_howto/loadbalancers.html">lb
worker</a> section.
+<b>lbfactor</b> property is used when working with a load balancer worker,
this is the load balancing factor for the worker.
+We'll see more on this in the <a
href="../common_howto/loadbalancers.html">load balancer worker</a> section.
</p>
<source>
# worker "worker1" will talk to Tomcat listening on machine www.x.com at
port 8007 using 2 lb factor
+ worker.worker1.type=ajp12
worker.worker1.host=www.x.com
worker.worker1.port=8007
worker.worker1.lbfactor=2
</source>
<p>
-Notes: In the ajpv12 protocol, connections are created, used and then closed
at each request.
-The default port for ajp12 is 8007
+Note: The default port for ajp12 is 8007
</p>
</subsection>
-<subsection name="ajp13 Worker properties">
+<subsection name="ajp13 Worker Properties">
<p>
-The ajp13 typed workers forward requests to out-of-process Tomcat workers
using the ajpv13 protocol over TCP/IP sockets.
-The main difference between ajpv12 and ajpv13 are that:
+The ajp13 typed workers forward requests to out-of-process Tomcat workers
using the ajp13 protocol over TCP/IP sockets.
+The main difference between ajp12 and ajp13 are that:
<ul>
<li>
-ajpv13 is a more binary protocol and it tries to compress some of the request
data by coding
+ajp13 is a more binary protocol and it tries to compress some of the request
data by coding
frequently used strings as small integers.
</li>
<li>
-ajpv13 reuses open sockets and leaves them open for future requests (remember
when you've got a Firewall between your
+ajp13 reuses open sockets and leaves them open for future requests (remember
when you've got a Firewall between your
web server and Tomcat).
</li>
<li>
-ajpv13 has special treatment for SSL information so that the container can
implement
+ajp13 has special treatment for SSL information so that the container can
implement
SSL related methods such as isSecure().
</li>
</ul>
@@ -205,12 +206,13 @@ SSL related methods such as isSecure().
</p>
<p>
-You should note that Ajp13 is now the only out-process protocol supported by
Tomcat 4 and above.
+You should note that ajp13 is the recommended protocol to connect to Tomcat.
</p>
<source>
# worker "worker2" will talk to Tomcat listening on machine www2.x.com at
port 8009 using 3 lb factor
+ worker.worker2.type=ajp13
worker.worker2.host=www2.x.com
worker.worker2.port=8009
worker.worker2.lbfactor=3
@@ -223,14 +225,14 @@ You should note that Ajp13 is now the on
</source>
<p>
-Notes: In the ajpv13 protocol, the default port is 8009
+Notes: In the ajp13 protocol, the default port is 8009
</p>
</subsection>
-<subsection name="lb Worker properties">
+<subsection name="lb Worker Properties">
<p>
-The load-balancing worker does not really communicate with Tomcat workers.
+The load balancing worker does not really communicate with Tomcat workers.
Instead it is responsible for the management of several "real" workers.
This management includes:
</p>
@@ -240,21 +242,22 @@ This management includes:
Instantiating the workers in the web server.
</li>
<li>
-Using the worker's load-balancing factor, perform weighed-round-robin load
balancing where
-high lbfactor means stronger machine (that is going to handle more requests)
+Using the worker's load balancing factor, perform weighted round-robin load
balancing where
+a higher lbfactor means stronger machine (that is going to handle
proportionally more requests)
</li>
<li>
-Keeping requests belonging to the same session executing on the same Tomcat
worker.
+Keeping requests belonging to the same session executing on the same Tomcat
worker
+(session stickyness).
</li>
<li>
-Identifying failed Tomcat workers, suspending requests to them and instead
falling-back on
+Identifying failed Tomcat workers, suspending requests to them and instead
failing over on
other workers managed by the lb worker.
</li>
</ul>
<p>
-The overall result is that workers managed by the same lb worker are
load-balanced
-(based on their lbfactor and current user session) and also fall-backed so a
single
+The overall result is that workers managed by the same lb worker are load
balanced
+(based on their lbfactor and current user session) and also fail over so a
single
Tomcat process death will not "kill" the entire site.
The following table specifies some properties that the lb worker can accept:
<ul>
@@ -288,7 +291,7 @@ Instead it is responsible for the load b
worker.jkstatus.type=status
</source>
<p>Next thing is to mount the requests to the jkstatus worker. For Apache
-web servers use the:</p>
+HTTP Servers use:</p>
<source>
# Add the jkstatus mount point
JkMount /jkmanager/* jkstatus
@@ -408,39 +411,36 @@ a sample worker.properties file is bundl
</p>
<p>
-You could also find here a sample workers.properties defining :
+You could also find here a sample workers.properties defining:
</p>
<ul>
<li>
-An ajp12 worker that used the host localhost and the port 8007
+Two ajp13 workers that use the host localhost and the ports 8109 and 8209
</li>
<li>
-An ajp13 worker that used the host localhost and the port 8008
-</li>
-<li>
-An lb worker that load balance the ajp12 and ajp13 workers
+An lb worker that load balances over the two ajp13 workers
</li>
</ul>
<source>
- # Define 3 workers, 2 real workers using ajp12, ajp13, the last one being a
loadbalancing worker
- worker.list=worker1, worker2, worker3
- # Set properties for worker1 (ajp12)
- worker.worker1.type=ajp12
- worker.worker1.host=localhost
- worker.worker1.port=8007
- worker.worker1.lbfactor=1
- # Set properties for worker2 (ajp13)
- worker.worker2.type=ajp13
- worker.worker2.host=localhost
- worker.worker2.port=8009
- worker.worker2.lbfactor=1
- worker.worker2.connection_pool_timeout=600
- worker.worker2.socket_keepalive=1
- worker.worker2.socket_timeout=60
- # Set properties for worker3 (lb) which use worker1 and worker2
- worker.worker3.balance_workers=worker1,worker2
+ # Define 3 workers, 2 real workers using ajp13, and one being a load
balancing worker
+ worker.list=node1, node2, lbworker
+ # Set properties for node1 (ajp13)
+ worker.node1.type=ajp13
+ worker.node1.host=localhost
+ worker.node1.port=8109
+ worker.node1.connection_pool_timeout=600
+ worker.node1.socket_keepalive=1
+ # Set properties for node2 (ajp13)
+ worker.node2.type=ajp13
+ worker.node2.host=localhost
+ worker.node2.port=8209
+ worker.node2.connection_pool_timeout=600
+ worker.node2.socket_keepalive=1
+ # Set properties for lbworker which uses node1 and node2
+ worker.lbworker.type=lb
+ worker.lbworker.balance_workers=node1,node2
</source>
</section>
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
