On Thu, 19 Sep 2002 23:49, you wrote:
> > OK, I understand now, your mod_jk.conf file just does the same as the
> > lines we have placed in httpd.conf but is designed to match a fresh
> > Tomcat install. So, you can either edit the mod_jk.conf file to match
> > your TDK setup or just configure things the way we have in httpd.conf.
>
> I would like to do it the way Tomcat does. I don;t want to mess with the
> Apache config every time the developers expand the application or add new
> ones. If tomcat creates the mod_jk.conf file for me, and I know it is
> correct, then all I have to do is restart apache. This is a lot easier
> than me reading the server.xml and then munging up the httpd.conf file
> to include the new settings. Is TDK's Tomcat an old version that does
> not include this feature?
I am not sure, I have never used this feature before :( However, there is no
reason you can't create this file yourself, include it in your httpd.conf and
just edit it when the developers add new web apps... although I can see how
the auto-generation would save a small amount of work, at least if you do it
manually you can't mess it up.
> > > > > In order to get this working, should I build Turbine from scratch
> > > > > or can someone help me out in getting Turbine working through
> > > > > Apache?
>
> So, should I try building Turbine from scratch, using a v4.0.4 of Tomcat
> or do you thing I am doing something wrong?
I have never tried to build a TDK from scratch myself, but I have heard that
it is not for the faint of heart (ie: only experienced Turbine developers
should even attempt it). Is there any reason why your developers can't just
use the TDK for development and then deploy their web apps onto a production
Tomcat 4.0.4? We don't install the TDK onto our production machines, we only
use the TDK for development of Turbine applications.
> With respect to the mod_jk.conf file, I downloaded one that John
> Turner had linked to on his howto page and I edited it to match my
> config (I think) and that is the config that I tested and did not work.
> Below is my server.xml, mod_jk.conf and httpd.conf files.
>
> Kent
>
> ################## start server.xml ##################
<snip>
> ################## end server.xml ##################
I noticed that you don't have an AJP Connector configured in your server.xml.
You have a WARP connector configured, but this is used for mod_webapp, not
mod_jk.
Add the following lines to your server.xml:
<!-- Define an AJP 1.3 Connector on port 8009 -->
<Connector className="org.apache.ajp.tomcat4.Ajp13Connector"
port="8009" minProcessors="5" maxProcessors="75"
acceptCount="10" debug="0"/>
> ################## start mod_jk.conf ##################
> JkMount /newapp/* ajp13
> JkMount /newapp/*.jsp ajp13
> JkMount /newapp/servlet/* ajp13
> JkMount /examples/jsp/security/protected/j_security_check ajp13
> JkMount /examples/CompressionTest ajp13
> JkMount /examples/SendMailServlet ajp13
> JkMount /examples/servletToJsp ajp13
> JkMount /examples/snoop ajp13
> JkMount /examples/*.jsp ajp13
> JkMount /examples/servlet/* ajp13
> JkMount /tomcat-docs/*.jsp ajp13
> JkMount /tomcat-docs/servlet/* ajp13
> #################### end mod_jk.conf ####################
You can see that the above URI paths are all being mapped to the "ajp13"
worker. Have you checked your workers.properties file? It should contain at
least the following lines:
worker.list=ajp13
worker.ajp13.port=8009
worker.ajp13.host=localhost
worker.ajp13.type=ajp13
> #################### start httpd.conf ####################
> LoadModule jk_module modules/mod_jk.so
> Include /home/apache/tdk/conf/mod_jk.conf
> #################### end httpd.conf ######################
Your httpd.conf looks OK to me.
Hope that helps,
-- Rodney
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
