I did mod_jk2 with Virtual Host, and while its not the same I think that doing VH will not be a problem once you get an idea of how it should/can be setup.

THIS IS PSEUDO, DO NOT TAKE AS GOSPEL TRUTH !!!!!!!!!!!!!!!  NO SUPPORT!  :p


-- workers.properties file --

# Setting Tomcat & Java Home
workers.tomcat_home=/usr/local/tomcat55
workers.java_home=/usr/local/java


ps=/
worker.list=host1
worker.ajp13.port=8009
worker.ajp13.host=localhost
worker.ajp13.type=ajp13

ps=/
worker.list=host2
worker.ajp13.port=9009
worker.ajp13.host=localhost
worker.ajp13.type=ajp13

ps=/
worker.list=host3
worker.ajp13.port=10009
worker.ajp13.host=localhost
worker.ajp13.type=ajp13

-- workers.properties file --


-- httpd.conf file --

<VirtualHost _default_:80>
ServerName host1:8009
DocumentRoot /usr/local/tomcat55/webapps/host1
DirectoryIndex index.html index.jsp
...
        <IfModule !mod_jk.c>
                LoadModule jk_module /usr/lib64/httpd/modules/mod_jk.so
                JkWorkersFile 
"/usr/local/tomcat55/conf/jk/host1-workers.properties"
                JkLogFile "/usr/local/tomcat55/logs/host1-mod_jk.log"
                JkLogLevel debug
                Alias / "/usr/local/tomcat55/webapps/host1"
                <Directory "/usr/local/tomcat55/webapps/host1">
                        Options Indexes +FollowSymLinks
                </Directory>
                JkMount /* host1
        </IfModule>
...
</VirtualHost>

<VirtualHost _default_:80>
ServerName host1:9009
DocumentRoot /usr/local/tomcat55/webapps/host2
DirectoryIndex index.html index.jsp
...
        <IfModule !mod_jk.c>
                LoadModule jk_module /usr/lib64/httpd/modules/mod_jk.so
                JkWorkersFile 
"/usr/local/tomcat55/conf/jk/host2-workers.properties"
                JkLogFile "/usr/local/tomcat55/logs/host2-mod_jk.log"
                JkLogLevel debug
                Alias / "/usr/local/tomcat55/webapps/host2"
                <Directory "/usr/local/tomcat55/webapps/host2">
                        Options Indexes +FollowSymLinks
                </Directory>
                JkMount /* host2
        </IfModule>
...
</VirtualHost>

-- httpd.conf file --

-- server.xml file --

<Host name="host1" debug="0" appBase="webapps/host1"
      unpackWARs="true" autoDeploy="true"
      xmlValidation="false" xmlNamespaceAware="false">
     ...
</Host>

-- server.xml file --



Try that and see how it works, again I did something similar with mod_jk2, I havent done this yet in mod_jk that is coming next. If you have different paths and arent putting the code in webapps, I currently have different paths for the different code, then the big change will be in the Server.xml where the appbase will need to be the full path to the code.

Let me know if this works or if you did any tweeks.

HTH

Dan


From: "Jonathan Woods" <[EMAIL PROTECTED]>
Reply-To: "Tomcat Users List" <users@tomcat.apache.org>
To: <users@tomcat.apache.org>
Subject: mod_jk configuration directives in VirtualHost sections
Date: Wed, 25 Jan 2006 21:55:55 -0000

Hello, list.

I have Apache 1.3.33 running on Linux and talking successfully to Tomcat
5.5.15 through mod_jk.  I'd now like to host multiple instances of Tomcat
(or maybe just multiple Tomcat connectors within one instance) to receive
requests dispatched at multiple VirtualHosts on the same server.

Is it possible to have more than one workers.properties file, and therefore
more than one JkWorkersFile directive, per Apache?  Ideally, I'd like one
workers.properties file per VirtualHost just to make app-building easier.
The documentation says that certain directives may be repeated in
VirtualHost sections - e.g. JkLogFile - but doesn't mention JkWorkersFile.

Thanks in advance -

Jon



---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to