The solution is to change JkMount /tomcat7* worker1 to JkMount /your-servlet-app* worker1. I used instead the name of the webapp as mount and everything is fine for me. Problem here, that he tries to access the exact same URI mounted, so in my case /tomcat7. I added 'JkMountCopy On' to my VirtualHost - and got first a Tomcat 404 (instead of the httpd 404). So the options set in nf weren't used in VirtualHosts. What is wrong?Īfter quanta hinted to set the log-level to debug (thanks) I did that and found the following error-message in mod_jk.log: 'jk_map_to_storage::mod_jk.c (3585): missing uri map for 176.9.9.55:/tomcat7/'. As far as I understand, I should see now the tomcat-site with But I get a 404 instead. Tomcat 7 is running and reachable under it's own port (8180, to not collide with tomcat6 from the package-system). Tomcat 7 is installed directly from archive from Apache, because it is not a package in Squeeze. My workers.properties look like this: # Define 1 real worker using ajp13 I commented out the loading of the module, because that already happens, after I installed mod_jk through the package-system (libapache2-mod-jk). # Send everything for context /examples to worker named worker1 (ajp13) # Update this path to match your logs directory location (put mod_jk.log next to access_log) # Update this path to match your local state directory or logs directory JkWorkersFile /etc/apache2/workers.properties # Update this path to match your conf directory location (put workers.properties next to nf) # Declare the module for (remove this line on Apache 2.x) # Update this path to match your modules location So I added the following to /etc/apache2/nf: # Load mod_jk module I only modified it a little to match directory-structure used on my Debian-(Squeeze)-System. I want to access Tomcat through the Apache-webserver using connectors.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |