On Thu, 19 Sep 2002 12:45, you wrote:
> On Thu, Sep 19, 2002 at 11:00:02AM +1000, Rodney Schneider wrote:
> > On Thu, 19 Sep 2002 07:34, you wrote:
> > > All,
> > >
> > > I am setting up Apache 2.0.40 to be the front end to a Turbine based
> > > app that some developers are building. I need this to work through
> > > Apache so we can protect the site with SSL.
> > >
> > > On the Tomcat list I found a really good how-to compiling mod_jk and
> > > getting it work with apache. (The howto is at
> > > http://www.johnturner.com/howto/apache-tomcat-howto.html)
> > > Unfortunately, the TDK test app would not work through Apache.
> >
> > Could you explain what you mean by "would not work"? What happened?
>
> I would get 404 errors from apache.
Was there anything in your apache error_log about mod_jk? Did you configure
mod_jk in your httpd.conf for this test, or include a modified mod_jk.conf?
We have the following lines in our httpd.conf:
--------
LoadModule jk_module libexec/mod_jk.so
<IfModule mod_jk.c>
JkWorkersFile /usr/local/tomcat/conf/jk/workers.properties
JkLogFile /var/apache/logs/mod_jk.log
JkLogLevel info
JkMount /kz/* kahootz
JkMount /index.jsp kahootz
</IfModule>
---------
Our workers.properties look like this:
---------
workers.tomcat_home=/usr/local/tomcat/bin
workers.java_home=/usr/local/jdk
# next is the path separator
ps=/
worker.list=kahootz
worker.kahootz.port=8009
worker.kahootz.host=localhost
worker.kahootz.type=ajp13
---------
Our Tomcat server.xml looks like this:
---------
<!-- 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"/>
---------
> > > To test my Apache
> > > configuration to see if the problem was there, I downloaded vanilla
> > > Tomcat 4.0.4 and configured it and Apache to work together. As I
> > > expected, Tomcat worked fine through Apache.
> >
> > When you say it worked fine, you mean you didn't have any problems at
> > all?
>
> The servlet or JSP would produce output that was rendered by my browser.
> I used the example applications that Tomcat came with.
>
> > > One of the things that I noticed that was not working the way it
> > > should was that mod_jk.conf was not being created automatically like
> > > it should (and was with the vanilla Tomcat install.) Is this a
> > > known issue?
> >
> > We use Apache 1.3.26 with mod_jk without problems, but I have never seen
> > a mod_jk.conf file... we configure mod_jk in httpd.conf and there is a
> > workers.properties file. What is supposed to be in mod_jk.conf?
>
> In $CATALINA_HOME/conf/auto (the auto directory is created if it is not
> there) Tomcat creates the mod_jk.conf file to INCLUDE in your httpd.conf
> file which contains the correct directory mapping to access the
> applications listed in the server.xml Here is the one that Tomcat created
> for me:
<snip>
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.
> > > In order to get this working, should I build Turbine from scratch or
> > > can someone help me out in getting Turbine working through Apache?
> >
> > I have never used Apache 2.0.x, only Apache 1.3.x, but I can try to help
> > if you ask questione on this list.
>
> Thanks. I can send my httpd.conf and server.xml as well if that helps.
> Also, let me know if you need any more info.
Hope that helps,
-- Rodney
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
