Etch Upgrade to Apache2 seems to have screwed tomcat
I just did an upgrade of my etch based server, and as part of the process it
seems to have completely screwed my apache setup.
I have got over most of the issues, but one is completely foxing me. That is
getting requests passed through to tomcat.
apache2.conf has the following lines to enable modules
# Include module configuration:
Include /etc/apache2/mods-enabled/*.load
Include /etc/apache2/mods-enabled/*.conf
and looking in /etc/apache2/modes-enabled/jk.conf I have
JkWorkersFile /etc/apache2/workers.properties
JkLogFile /var/log/apache2/mod_jk.log
JkLogLevel info
JkMountFile /etc/apache2/urimap.properties
JkLogStampFormat "[%a %b %d %H:%M:%S %Y] "
JkRequestLogFormat "%U%q"
JkOptions +ForwardDirectories
JkShmFile /var/log/apache2/jk-runtime-status
and /etc/apache2/urimap.properties
has amongst other lines this
/blog/app=tomcat
where the workers.properties file defines tomcat
worker.list=tomcat
worker.tomcat.type=ajp13
worker.tomcat.host=appserv.home
worker.tomcat.port=8009
worker.tomcat.connect_timeout=10
So when I call up my website with a url of www.chandlerfamily/blog/app
I would expect tomcat to be passed that url rather than apache attempt to look
it up. I get this is an unkown url error when I do try and access it, with
the log having
[Sun Oct 29 22:19:59 2006] [error] [client 192.168.0.21] File does not
exist: /var/lib/tomcat5/webapps/blog/app
[Sun Oct 29 22:23:22 2006] [error] [client 192.168.0.21] File does not
exist: /var/lib/tomcat5/webapps/blog/app
which implies to me that its attempting to look for that file rather than
passing it thought to tomcat.
This was working before the upgrade, so any ideas where to look now?
--
Alan Chandler
http://www.chandlerfamily.org.uk
Reply to: