Denese:
libexec/mod_jk.so is correct---that's where mod_jk is located.
So I added ApacheConfig modJk=/usr/local/apache-1.3.27/libexe/ to
httpd.conf, as suggested in the catalina.out error message (thought
maybe a full path would help), but Apache won't start---says
ApacheConfig is invalid.
This would be because ApacheConfig goes in Tomcat's 'server.xml' file
(except with a different syntax). The log message could be better (it's
left over from Tomcat 3.3) :-(.
The warning is simply because Tomcat has no way of knowing about your Apache
install, so it is simply telling you that it
Bill:
I added the listener line exactly as you showed it (actually, the line
was already there but without the modJk=... part), and I still get
these messages in catalina.out:
mod_jk location:
/usr/local/webserver/jakarta-tomcat-4.1.12-LE-jdk14/libexec/mod_jk.so
Make sure it is installed
Sorry, my fault. ApacheConfig requires the full path to mod_jk.so to
suppress the warning. Specifying the correct relative path will work fine
with Apache (and just create the warning in the log that can be safely
ignored).
Jerry Ford [EMAIL PROTECTED] wrote in message
[EMAIL
Jerry - you know that is the exact error message that I was getting at one
point. Here two things that I did. I realized that the mod_jk.conf was
being generated every time I started Tomcat. So any changes that I made to
it were being overwritten every time I used it. The generated mod_jk.conf
