Hang on Jeff this isn't correct is it? mod_jk can support either the ajp12
or ajp13 protocol so adding the ajp13 connector to server.xml isn't likely
to help.
I'm afraid I can't help with the jsp side of things as I only ever
write servlets. Might be interesting to see if you can get a servlet
to work to see if JSP issue.
andrew
On Sun, 29 Jul 2001, you wrote:
> If you're using mod_jk, you have to add the connector to your server.xml
> file. I'm not sure why you *haven't* done that. Apache and Tomcat won't be
> able to communicate without it. So, I would suggest starting there.
>
> --jeff
>
> ----- Original Message -----
> From: "Kelly E. Grooms" <[EMAIL PROTECTED]>
> To: <[EMAIL PROTECTED]>
> Sent: Saturday, July 28, 2001 2:50 PM
> Subject: Apache cannot connect to Tomcat
>
>
> > Hello,
> >
> > I've scoured the web and all the Tomcat lists that I can find and still
> > cannot solve this error. Everything works fine through port 8080 as
> > stand-alone, but when I try accessing Tomcat through Apache the page times
> > out with no output from the JSP. Afterward my mod_jk.log file contains:
> >
> > [jk_connect.c (143)]: jk_open_socket, connect() failed errno = 110
> > [jk_ajp12_worker.c (152)]: In jk_endpoint_t::service, Error sd = -1
> >
> > I compiled mod_jk.so myself. I've added mod_jk.conf-auto to my httpd.conf
> > file. I altered workers.properties to reflect my JAVA_HOME, TOMCAT_HOME
> and
> > file separator ("/"). I have _not_ added the connector for ajp13 to my
> > server.xml file.
> >
> > Here is my configuration:
> >
> > Mandrake Linux 8.0
> > Apache 1.3.19
> > Java 1.3.1 (from Sun)
> > Tomcat 3.2.3
> >
> > I've installed older versions of Tomcat on other configurations in the
> past
> > and did not have this much trouble. I'm beginning to feel very
> discouraged.
> > Can anyone help? Thanks.
> >
> > Kelly E. Grooms
> > [EMAIL PROTECTED]
> >
--
Andrew Robson
tel: (0141) 424 0607
mobile: 07759 430234
email: [EMAIL PROTECTED]
