tomcat-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Stephen Jones" <stevejo...@qwest.net>
Subject Bugzilla #512 is Bunk
Date Thu, 01 Mar 2001 04:08:48 GMT
The following bug is not a bug:
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=512

In httpd.conf, you cannot do this:

<VirtualHost .... blah>
     .... normal config for VirtualHost ...
     Include /usr/local/jakarta-tomcat/conf/mod_jk.conf-auto
</VirtualHost>

There are three main purposes of including mod_jk.conf-auto:

(1) To get the mod_jk Apache Module loaded, as follows:
      LoadModule jk_module libexec/mod_jk.so

(2) To configure Apache for your Tomcat Contexts using Alias, Location,
and Directory Apache Directives

(3) To configure mod_jk itself using all the directives starting with Jk
(JkWorkersFile, JkLogFile, JkMount, etc).

The first (1) Apache directive is the problem: the LoadModule directive
is illegal within the VirtualHost context.
(See http://httpd.apache.org/docs/mod/mod_so.html#loadmodule )

The directives in (2) are definitely legal, but I don't know about those
in (3) since they are custom. Does anyone know whether these would work
within the VirtualHost context?

The bug was reported by someone using Apache 1.3.14; they recieved a
core dump dereferencing a null pointer to something that was supposed to
contain Apache configuration info (a jk_server_conf_t).
I am using Apache 1.3.17; I recieved this polite and informative (wow,
from open source software?) error message:

sudo /usr/local/apache/bin/apachectl startssl
Syntax error on line 8 of /usr/local/tomcat/conf/mod_jk.conf-auto:
LoadModule cannot occur within <VirtualHost> section
/usr/local/apache/bin/apachectl startssl: httpd could not be started

Provided that the custom directives (3) will work within a VirtualHost
context, the solution to this problem is to create a custom
configuration file based on mod_jk.conf-auto, move the LoadModule
directive into it, and then Include it from within your VirtualHost
context.

If the directives (3) do work, another option would be for Tomcat to
change the code to not generate the LoadModule directive, which prevents
this level of configurability, and just make people type it in.

Hope this is helpful,
Steve Jones


Mime
View raw message