On Tue, Sep 17, 2002 at 02:41:36PM -0400, Turner, John wrote:
The last time I saw my name that many times at once in print, I was getting
yelled at. :)
Your Listener elements look fine, and they are in the right place.
Can you take a couple of minutes and try it with a vanilla Tomcat install?
The binary install takes about 5 minutes to setup on Redhat...it would tell
you right away if it was a tomcat vs. Turbine/Tomcat thing, or something
deeper.
Well, I downloaded Tomcat4.0.4 (since this is what I think TDK 2.1 uses),
copied my httpd.conf for my turbine instance for use with tomcat (changing
the paths to point to tomcat, not turbine of course) and everything works
fine through apache. Even the mod_jk.conf file is created.
I guess I will go over to the turbine list and bug them now unless
someone here has an idea on what is going on.
Kent
John
-Original Message-
From: Kent Perrier [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, September 17, 2002 2:28 PM
To: [EMAIL PROTECTED]
Subject: Question regarding mod_jk configuration
I have built mod_jk according to John Turner's howto for
Tomcat 4, apache
2 and redhat. The only difference is that I am using the Turbine Dev
Kit, not a vanilla tomcat install. Anyway, I get the plugin installed
and /server-info/ shows mod_jk loaded. John states in the
howto that tomcat
creates the mod_jk.conf file, but mine does not when it starts. Does
anyone have any idea where I would look to find out why? I
have downloaded
the mod_jk.conf that John has on his site so that I have one
and I have
edited it to match my configuration. I can access the /examples and
/newapp/servlet/newapp (the default turbine app) fine from
localhost:8080,
but I cannot access them from apache on port 80. (A
clarification: when I
access /examples, I get the apache directory listing, but it
looks a lot
different from what I see when I access
localhost:8080/examples. Looking in
the examples directory I see:
[polaris:/home/apache/tdk/examples]# find . -print
.
./actions
./actions/TestGlobalCache.java
./scheduledjobs
./scheduledjobs/DefaultScheduledJob.java
./WebMacro.properties
so I guess that the Turbine folks nuter the Tomcat example.
If not, please
correct me.)
So, in summary, my questions are (1) why isn't mod_jk.conf
being generated
automagically as John's HowTo states and (2) why am I getting
404 errors
when I attempt to access the Turbine default app via apache at
/newapp/servlet/newapp/
Below are my httpd.conf, server.xml and (finally) mod_jk.conf
Thanks!
Kent
--
To unsubscribe, e-mail: mailto:[EMAIL PROTECTED]
For additional commands, e-mail: mailto:[EMAIL PROTECTED]
--
To unsubscribe, e-mail: mailto:[EMAIL PROTECTED]
For additional commands, e-mail: mailto:[EMAIL PROTECTED]
