Hi,
I am having some grief with a new tomcat/mod_jk installation. I've
installed the required context in server.xml, and have used the
auto-generated apache mod_jk config file to taylor httpd.html.
The configured URL works great from the tomcat webserver running on port
8080 by default, but accessing the URL through Apache and mod_jk results
in an error 404 in the Apache logfile. A packet sniff on port 8009
indicates no traffic at all - which suggests to me that the Apache side
is broken, but I don't understand this stuff clearly enough yet to see
through the fog, and the FAQ hasn't yielded any clues. I have put the
following into the relevant virtual host config on Apache:
Alias /thh "/var/tomcat/webapps/thh"
<Directory "/var/tomcat/webapps/thh">
Options Indexes FollowSymLinks
</Directory>
JkMount /thh/servlet/* ajp13
JkMount /thh/*.jsp ajp13
<Location "/thh/WEB-INF/">
AllowOverride None
deny from all
</Location>
<Location "/thh/META-INF/">
AllowOverride None
deny from all
</Location>
The context in the server.xml file looks like this:
<Context path="/thh"
docBase="webapps/thh"
crossContext="true"
debug="0"
reloadable="true"
trusted="false" >
</Context>
In the mod_jk.log file there have been some strange messages logged -
but there is no indication of whether these messages are just debug
informational statements, or whether they indicate an error condition of
some kind:
[jk_uri_worker_map.c (335)]: jk_uri_worker_map_t::uri_worker_map_close,
NULL parameter
[jk_uri_worker_map.c (185)]: In
jk_uri_worker_map_t::uri_worker_map_free, NULL parameters
Does this ring any bells with anyone? Just how stable is mod_jk -> as an
alternative we've been considering hiding the tomcat webserver behind
Apache mod_proxy instead of using mod_jk - any comments on this
alternative config?
Regards,
Graham
--
-----------------------------------------
[EMAIL PROTECTED] "There's a moon
over Bourbon Street
tonight..."
S/MIME Cryptographic Signature
