tomcat-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Simon Pabst <>
Subject Re: mod_jk.conf-auto or /auto/mod_jk.conf (J. Turner)?
Date Sun, 20 Jul 2003 13:45:25 GMT
Coyote is not synonym for jk2, its just the new Tomcat Connector name,

which you can use for HTTP (as in your case on port 8180),
and AJP13 connections for both mod_jk 1 and 2 (on 8009 with 

for a list.

So everything should be all right.

At 15:25 20.07.2003 +0200, you wrote:
>never having trouble with Apache 1.3, TomCat 3.x and mod_jk 1.2 - now -
>after upgrading to TomCat 4.1.24 I do not succeed in configuring the
>system to be accessible via port 80.
>I found following web sites that are recommended for getting information
>about how to integrate mod_jk (jk) with Apache 1.3.x and TomCat 4.x:
>While under one can read that
>"Include /var/tomcat3/conf/jk/mod_jk.conf-auto"
>"... will tell Apache to use directives in the mod_jk.conf-auto file in
>the Apache configuration.
>This file is created by enabling the Apache auto-configuration as
>described in the Tomcat documentation. .."
>on John Turner´s web site you find following hint:
>"... add the following line at the very end: Include
>Note: the mod_jk.conf file gets created by Tomcat when Tomcat starts. It
>gets created every time Tomcat starts. So, if you have your server.xml
>configured, you can ignore httpd.conf (in most cases) except to add the
>Include directive for mod_jk.conf. You don't need to create or edit
>mod_jk.conf. ...".
>Well - following John´s instructions - I inserted following lines in my
>server.xml - which btw - is not mentioned with any word under the
>jakarta howto above:
><Host ...
><Listener className="org.apache.ajp.tomcat4.config.ApacheConfig"
>modJk="/usr/local/apache2/modules/" />
><Server ..
><Listener className="org.apache.ajp.tomcat4.config.ApacheConfig"
>append="true" forwardAll="false"
>modJk="/usr/local/apache2/modules/" />
>Moreover I commented out following line in the server.xml:
><Connector className="org.apache.ajp.tomcat4.Ajp13Connector"
>   port="8009" minProcessors="5" maxProcessors="75"
>   acceptCount="10" debug="0"/>
>and "disabled" those lines:
>     <Connector className="org.apache.coyote.tomcat4.CoyoteConnector"
>                port="8009" minProcessors="5" maxProcessors="75"
>                enableLookups="true" redirectPort="8443"
>                acceptCount="10" debug="0" connectionTimeout="0"
>                useURIValidationHack="false"
>because they refer to the same port 8009 like the
>org.apache.ajp.tomcat4.Ajp13Connector class.
>(IS that correct? I only want to use jk and NOT jk2 - but nevertheless I
>find following line in the catalina.log after starting TomCat 4.1.24 ->
>[INFO] Http11Protocol - -Starting Coyote HTTP/1.1 on port 8180 - Isn´t
>Coyote the synonym for jk2 ?):
>Starting TomCat 4.1.24 results in being able to access the example
>servlets via
>Under  /usr/local/jakarta-tomcat4.1/conf/auto/ a file mod_jk.conf is
>created (so neither conf/jk/mod_jk.conf-auto NOR conf/auto/mod_jk.conf )
>but without any text - it is empty.
>Hence I cannot "tell" Apache via the httpd.conf to include an "empty"
>Why are there those different descriptions going around? And does
>anybody know how I can make my system produce a mod_jk.conf file for
>including it in Apache?
>Thanks and best regards
>To unsubscribe, e-mail:
>For additional commands, e-mail:

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message