Author: rjung
Date: Tue Sep 1 14:24:56 2015
New Revision: 1700569
URL: http://svn.apache.org/r1700569
Log:
Fix some typos, apply some reqording and minor
clarifications.
Modified:
tomcat/jk/trunk/xdocs/miscellaneous/faq.xml
Modified: tomcat/jk/trunk/xdocs/miscellaneous/faq.xml
URL:
http://svn.apache.org/viewvc/tomcat/jk/trunk/xdocs/miscellaneous/faq.xml?rev=1700569&r1=1700568&r2=1700569&view=diff
==============================================================================
--- tomcat/jk/trunk/xdocs/miscellaneous/faq.xml (original)
+++ tomcat/jk/trunk/xdocs/miscellaneous/faq.xml Tue Sep 1 14:24:56 2015
@@ -45,7 +45,7 @@ the mail list archive</a>
before you post questions to the list.
If you are unable to locate the answer to your question in the archive,
you can post questions about JK to the user list for assistance.
-Make sure that you include the version of your Webserver,
+Make sure that you include the version of your web server,
that you are using as well as the platform you are running on
and go
<a href="http://tomcat.apache.org/lists.html";>
@@ -66,25 +66,28 @@ Tomcat Connectors (mod_jk, mod_jk2) Down
<subsection name="What's the difference between JK and mod_jk ?">
<br />
<p>
-<b>JK</b> is a project covering web-servers to Tomcat connectors,
-whereas <b>mod_jk</b> is the <a href="../webserver_howto/apache.html">Apache
module</a> developed in JK.
+<b>JK</b> is a project covering web servers to Tomcat connectors.
+</p>
+<p>
+<a href="../webserver_howto/apache.html">Apache HTTP Server</a> support is
implemented on JK, using a plugin
+called the <b>mod_jk module</b>.
</p>
<p>
-<a href="../webserver_howto/iis.html">IIS webserver</a>support is implemented
on JK, using a redirector
-called <b>isapi redirector</b>.
+<a href="../webserver_howto/iis.html">Microsoft IIS</a> support is implemented
on JK, using a plugin
+called the <b>ISAPI redirector</b>.
</p>
<p>
-<a href="../webserver_howto/nes.html">Netscape/SunONE/Sun
webserver</a>webserver support is implemented on JK, using a redirector
-called <b>nsapi redirector</b>.
+<a href="../webserver_howto/nes.html">iPlanet Web Server</a> support is
implemented on JK, using a plugin
+called the <b>NSAPI redirector</b>.
</p>
</subsection>
<subsection name="Where can I get more information ?">
<p>
-For <b>JK 1.2.x</b>, you should read :
+For <b>JK 1.2.x</b>, you should read:
</p>
<ul>
@@ -94,15 +97,15 @@ For <b>JK 1.2.x</b>, you should read :
</li>
<li>
-<a href="../webserver_howto/apache.html">Apache and JK</a>
+<a href="../webserver_howto/apache.html">Apache HTTP Server and JK (mod_jk)</a>
</li>
<li>
-<a href="../webserver_howto/iis.html">IIS and JK</a>
+<a href="../webserver_howto/iis.html">Microsoft IIS and JK (ISAPI
redirector)</a>
</li>
<li>
-<a href="../webserver_howto/nes.html">Netscape/SunONE/Sun and JK</a>
+<a href="../webserver_howto/nes.html">iPlanet Web Server and JK (NSAPI
redirector)</a>
</li>
<li>
@@ -116,23 +119,20 @@ You could also try searching the mailing
</p>
</subsection>
-<subsection name="Which protocol should I use? Ajp12 or Ajp13?">
+<subsection name="Which protocol should I use - ajp12, ajp13 or ajp14?">
<p>
-<a href="../ajp/ajpv13a.html">Ajp13</a> is a newer protocol, it's faster, and
it works better with SSL.
-You almost certainly want to use it now that <strong>ajp12 is
deprecated</strong>.
+<a href="../ajp/ajpv13a.html">ajp13</a> is the standard. The old
+<strong>ajp12 is deprecated</strong> and <strong>ajp14 is
experimental</strong>.
</p>
<p>
-Also ajp13 is supported by all Apache Tomcat versions starting with Tomcat 3.2.
-</p>
-
-<p>
-Others Servlet engines like <b>jetty</b> have support for Ajp13.
+Also ajp13 is supported by all Apache Tomcat versions starting with Tomcat 3.2
+and by other servlet engines like <b>Jetty</b> and <b>JBoss</b>.
</p>
</subsection>
<subsection name="I've got a firewall between my web server and Tomcat which
drops ajp13 connections after some time">
<p>
-Ajp13 uses persistant connections where the traffic could be null if there is
no request to be sent to Tomcat.
+The ajp13 protocol uses persistant connections where the traffic could be null
if there is no request to be sent to Tomcat.
Firewalls use to drop inactive connections and will make your web server and
Tomcat think the connection is valid.
</p>
<p>
@@ -143,12 +143,12 @@ If nothing else helps, you can try <b>Jk
</p>
</subsection>
-<subsection name="Under heavy load, I've got many threads in Tomcat even if my
Apache Web Server handles much of the load">
+<subsection name="Under heavy load, I've got many threads in Tomcat even if my
Apache HTTP Server handles much of the load">
<p>
-Under heavy load, Apache Web Server creates many children to handle the load,
+Under heavy load, the Apache HTTP Server creates many children to handle the
load,
which will in turn create many connections
to Tomcat to forward the requests they should handle.
-Apache Web Server will normally kill the children/threads when the load
decreases.
+The Apache HTTP Server will normally kill the children/threads when the load
decreases.
But if the load is still there and even if only Apache handles the requests,
ie static contents, the children are kept and with them all the ajp13
connections,
even if they are no more used.
@@ -161,14 +161,14 @@ for more informations refer to <a href="
</section>
-<section name="Apache">
+<section name="Apache HTTP Server">
<p>
-Informations and FAQ about mod_jk and Apache Web Servers.
+Informations and FAQ about mod_jk and the Apache HTTP Server.
</p>
<subsection name="Whenever I restart Tomcat, Apache locks up!">
<p>
-The Ajp13 protocol keeps an open socket between Tomcat and Apache.
-Release of mod_jk present in J-T-C handles the network failure.
+The ajp13 protocol keeps an open socket between Tomcat and Apache.
+Release of mod_jk present in Tomcat Connectors handles the network failure.
But with very ancient releases of mod_jk, you may have to restart Apache as
well.
</p>
</subsection>
@@ -194,7 +194,7 @@ You should use <b>mod_jk.so-noeapi</b> o
<p>
It's wise to avoid using EAPI modules on STD API Apache or to use standard API
modules on EAPI Apache.
-Allways be sure to have the <b>mod_jk.so</b> witch match your version of Apache
+Allways be sure to have the <b>mod_jk.so</b> which match your version of
Apache.
</p>
</subsection>
@@ -202,7 +202,7 @@ Allways be sure to have the <b>mod_jk.so
<p>
It's related to Apache EAPI, the message <code>'mod_jk.so is garbled - perhaps
this is not an Apache module DSO ?'</code>
just told you, that your're trying to install a mod_jk.so DSO module that was
compiled on an Apache using EAPI,
-like apache-mod_ssl or apache from Redhat distro 6.2/7.0 but your system use
the standard apache with normal API.
+like apache-mod_ssl or apache from Redhat distro 6.2/7.0 but your system use
the standard Apache with normal API.
</p>
</subsection>
@@ -219,7 +219,7 @@ Apache with standard API and you try to
APXS is a Perl script that is created when you build the Apache web server
from source.
Chances are that if you are getting these errors and you obtained Apache as a
binary distribution,
that APXS is not configured correctly for your system.
-Your best bet is to get the Apache source from http://httpd.apache.org and
build it yourself.
+Your best bet is to get the Apache source from the <a
href="http://httpd.apache.org/";>Apache HTTP Server homepage</a> and build it
yourself.
Use the following for a basic build (read the Apache docs for other options):
<screen>
<type>cd /usr/local/src</type><br/>
@@ -252,7 +252,7 @@ Apache 2.x.y the resulting binary should
is bigger or equals to y. If you also need compatibility for versions 2.x.z
with z smaller than y, use the configure flag --enable-api-compatibility. Note
that the module compiled with any 2.x will never be compatible with 2.y for
-x different from y.
+x different from y. In this case you need to recompile the module.
</p>
</subsection>
@@ -261,9 +261,9 @@ x different from y.
mod_jk works well with Apache 2.x from 2.0 to 2.4.
</p>
<p>
-Important parts of the functionality of mod_jk have been reimplemented as
Apache httpd modules mod_proxy_ajp
-and mod_proxy_balancer. These are part of the standard distributoin of Apache
2.2. The new modules do not contain
-all features of mod_jk, but you get them automatically with every Apache 2.2
and later.
+Important parts of the functionality of mod_jk have been reimplemented in the
Apache HTTP Server modules mod_proxy_ajp
+and mod_proxy_balancer. These are part of the standard distribution of Apache
2.2 and 2.4. The new modules do not contain
+all features of mod_jk, but on the other hand you get the modules
automatically with every new Apache release.
</p>
</subsection>
@@ -289,7 +289,7 @@ to Apache 2.x to support JNI.
<subsection name="JNI report that JVM couldn't be started under Linux">
<warn>JNI workers have been deprecated. They will likely not work. Do not use
them.</warn>
<p>
-Under Linux, you should set some environment variables BEFORE launching your
Apache server :
+Under Linux, you should set some environment variables BEFORE launching your
Apache HTTP Server:
</p>
<screen>
@@ -298,7 +298,7 @@ Under Linux, you should set some environ
<p>
Also some Linux distributions have enabled a GLIBC feature called 'floating
stacks' which may not works with kernel
-less than 2.4.10 on SMP machines. You should disable floating stacks by
exporting an environment variable :
+less than 2.4.10 on SMP machines. You should disable floating stacks by
exporting an environment variable:
</p>
<screen>
@@ -307,7 +307,7 @@ less than 2.4.10 on SMP machines. You sh
<p>
You could have to update your service scripts, ie
<b>/etc/rc.d/init.d/httpd</b>, to set these env vars
-before your httpd server starts.
+before your Apache server starts.
</p>
</subsection>
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
