mturk 2004/12/18 04:48:34
Modified: jk/xdocs/config apache.xml workers.xml
Log:
Run spell checker. Sorry, but there is still no grammar checker :)
Revision Changes Path
1.10 +10 -10 jakarta-tomcat-connectors/jk/xdocs/config/apache.xml
Index: apache.xml
===================================================================
RCS file: /home/cvs/jakarta-tomcat-connectors/jk/xdocs/config/apache.xml,v
retrieving revision 1.9
retrieving revision 1.10
diff -u -r1.9 -r1.10
--- apache.xml 13 Dec 2004 09:46:29 -0000 1.9
+++ apache.xml 18 Dec 2004 12:48:33 -0000 1.10
@@ -46,10 +46,10 @@
error or trace
</p></attribute>
<attribute name="JkLogStampFormat" required="false"><p>
-The Jakarta Tomcat Connector module <b>date</b> log format, follow strftime
synthax
+The Jakarta Tomcat Connector module <b>date</b> log format, follow strftime
syntax
</p></attribute>
<attribute name="JkRequestLogFormat" required="false"><p>
-Request log format string. See datailed description below.
+Request log format string. See detailed description below.
</p></attribute>
<attribute name="JkAutoAlias" required="false"><p>
Automatically Alias webapp context directories into the Apache
@@ -75,7 +75,7 @@
</p></attribute>
<attribute name="JkOptions" required="false"><p>
Set one of more options to configure the mod_jk module. See below for
-deatails about this directive
+details about this directive
</p></attribute>
<attribute name="JkEnvVar" required="false"><p>
Adds a name of environment variable that should be sent to servlet-engine
@@ -151,7 +151,7 @@
</p>
<p>
-<b>JkLogStampFormat</b> will configure the date/time format found on mod_jk
logfile.
+<b>JkLogStampFormat</b> will configure the date/time format found on mod_jk
log file.
Using the strftime() format string it's set by<br />
default to <b>"[%a %b %d %H:%M:%S %Y]"</b>
</p>
@@ -169,7 +169,7 @@
<b>JkRequestLogFormat</b> will configure the format of mod_jk individual
request logging.
Request logging is configured and enabled on a per virtual host basis.
To enable request logging for a virtual host just add a JkRequestLogFormat
config.
-The syntax of the format string is similiar to the Apache LogFormat command,
+The syntax of the format string is similar to the Apache LogFormat command,
here is a list of the available request log format options:
</p>
@@ -357,8 +357,8 @@
<source>
# do not send requests ending with .gif to worker1
JkUnMount /*.gif worker1
- # The .gif files will not be mouted cause JkUnMount takes
- # precedance over JkMount directive
+ # The .gif files will not be mounted cause JkUnMount takes
+ # precedence over JkMount directive
JkMount /servlet/*.gif worker1
</source>
@@ -397,12 +397,12 @@
</p>
<p>
<b>JkWorkerProperty</b> is a new directive available from JK 1.2.7
-version. It is a convinient method for seting directives that are
-usualy set insice <b>workers.propeties</b>file. The parameter for
+version. It is a convenient method for setting directives that are
+usually set inside <b>workers.propeties</b>file. The parameter for
that directive is raw line from workers.properties file.
</p>
<source>
- # Just like workers.properties but exach line is prefixed
+ # Just like workers.properties but exact line is prefixed
# with JkWorkerProperty
# Minimal jk configuration
1.8 +24 -17 jakarta-tomcat-connectors/jk/xdocs/config/workers.xml
Index: workers.xml
===================================================================
RCS file: /home/cvs/jakarta-tomcat-connectors/jk/xdocs/config/workers.xml,v
retrieving revision 1.7
retrieving revision 1.8
diff -u -r1.7 -r1.8
--- workers.xml 14 Dec 2004 08:48:07 -0000 1.7
+++ workers.xml 18 Dec 2004 12:48:33 -0000 1.8
@@ -46,8 +46,6 @@
Tomcat workers are defined in a properties file dubbed
<b>workers.properties</b> and this tutorial
explains how to work with it.
</p>
-<p>The generic workers.properties directive is in the form:</p>
-<p><strong>worker.<worker
name>.<directive>=<value></strong></p>
</section>
<section name="Directives">
@@ -62,11 +60,13 @@
</p>
<subsection name="Defining workers">
+<p>The generic workers.properties directive is in the form:</p>
+<p><strong>worker.<worker
name>.<directive>=<value></strong></p>
<p>Defining workers to the Tomcat web server plugin can be done using a
properties file
(a sample file named workers.properties is available in the conf/ directory).
</p>
<directives>
-<directive name="worker.list" required="true">
+<directive name="worker.list" default="ajp13" required="true">
A comma separated list of workers names that the JK will use. When starting
up,
the web server plugin will instantiate the workers whose name appears in the
worker.list property, these are also the workers to whom you can map
requests.
@@ -93,18 +93,20 @@
<subsection name="Connection directives">
<p>Connection directives defines the parameters needed to connect and
maintain
-the connections pool of persisten connections between JK and remote Tomcat.
+the connections pool of persistent connections between JK and remote Tomcat.
</p>
<directives>
-<directive name="host" default="localhost" required="true">
+<directive name="host" default="localhost" required="false">
Host name or IP address of the backend Tomcat instance. The remote Tomcat
must
support the ajp13 protocol stack. The host name can have a <b>port</b> number
-embedded separated by the colon (':') character.
+embedded separated by the colon (':') character.
</directive>
<directive name="port" default="8009" required="false">
Port number of the remote Tomcat instance listening for defined protocol
requests.
+The default value depends on the worker type. For AJP13 workers the default
port is
+<b>8009</b>, while for AJP14 type of worker that value is <b>8011</b>.
</directive>
<directive name="socket_timeout" default="0" required="false">
@@ -122,7 +124,7 @@
To enable keepalive set this property value to the number greater then
<b>0</b>.
<p>
The problem with Firewall cutting inactive connections is that sometimes,
neither webserver or tomcat
-have informations about the cut and couldn't handle it.
+have information about the cut and couldn't handle it.
</p>
</directive>
@@ -143,12 +145,17 @@
</directive>
<directive name="cachesize" default="1" required="false">
-Cachesize property is usefull when you're using JK in multithreaded
-web servers such as Apache 2.0 (worker), IIS and Netscape. They will benefit
the most by
-setting this value to a higher level (such as the estimated average
concurrent users for Tomcat).
-If cachesize is not set, the connection cache support is disabled.
-Cachesize determines the minimum number of open connections to backend
Tomcat.
-<warn>Do not use cachesize with values higer then 1 on <b>prefork mpm</b> or
<b>apache 1.3.x</b>!</warn>
+Cachesize defines the number of connections made to the AJP backend that
+are maintained as a connection pool.
+It does not limit the number of those connection.
+<p>
+Cachesize property is useful when you're using JK in multi threaded
+web servers such as Apache 2.0 (worker), IIS and Netscape. The cachesize
property
+should reflect the number of threads per child process. The JK 1.2.8 will
discover
+the number of threads per child process on Apache 2 web server with
worker-mpm.
+For other web servers to will have to set that value manually.
+</p>
+<warn>Do not use cachesize with values higher then 1 on <b>prefork mpm</b>
or <b>apache 1.3.x</b>!</warn>
</directive>
<directive name="cache_timeout" default="0" required="false">
@@ -187,7 +194,7 @@
are member of load balancer must not appear in the <b>worker.list</b>
directive.
</p>
<p>Loadbalancer directives defines the parameters needed to create a workers
that are
-connectiong to a remote cluster of backend Tomcat servers. Each cluster node
has to
+connecting to a remote cluster of backend Tomcat servers. Each cluster node
has to
have a worker defined.
</p>
<p>
@@ -241,7 +248,7 @@
</subsection>
<subsection name="Advanced worker directives">
-
+<br />
<directives>
<directive name="connect_timeout" default="0" required="false">
Connect timeout property told webserver to send a PING request on ajp13
connection after
@@ -267,7 +274,7 @@
Reply_timeout property told webserver to wait some time for reply to a
forwarded request
before considering the remote tomcat is dead and eventually switch to
another tomcat in a cluster
group. By default webserver will wait forever which could be an issue for
you.
-The parameter is the number of milliseconds to wait for reply, so adjust it
carrefully if you
+The parameter is the number of milliseconds to wait for reply, so adjust it
carefully if you
have long running servlets.
<p>
This features has been added in <b>jk 1.2.6</b> to avoid problem with hung
tomcat's and works on all
@@ -336,7 +343,7 @@
the other worker will only be checked if a request with a session id of this
worker comes in.
</p>
<p>
-Why do we need souch a complex behavior ?
+Why do we need such a complex behavior ?
</p>
<p>
We need a graceful shut down of a node for maintenance. The balancer in
front asks a special port on each
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
