On Mon, 23 Dec 2002, Denise Mangano wrote: > Tomcat is up and running - I can view and execute examples by using > :8080.
OK, that means Tomcat standalone is working (as controlled by the Coyote Http Connector onport 8080) > If the port that Tomcat is listening on is set by > workers.properties, then that would be port 8009. Where Apache is > expecting it to listen on I am not sure. Actually, you've got it backwards. workers.properties is part of the Apache config, and indicates where Apache is expecting to find the (Tomcat side of the) Ajp connector. server.xml is part of the Tomcat config, and tells Tomcat where it should listen for Ajp (and other protocols). > The email I sent was > correct - the uncommented ports are those that were listed. The > only difference between the two is the connection Timeout > settings... ( I posted the correct server.xml file - the second > email contains the correct one). I responded to that email -- and in fact the connection timeout was the only thing that looked odd to me. So that might be what's causing the problem. > -----Original Message----- > From: Milt Epstein [mailto:[EMAIL PROTECTED]] > Sent: Monday, December 23, 2002 11:27 AM > To: Tomcat Users List > Subject: Re: Mod_jk - won't execute jsp or servlets > > > On Mon, 23 Dec 2002, Denise Mangano wrote: > > > Thanks to all your help, I've gotten over some bumps. As it stands I > > can access any static pages in the Tomcat directory without having to > > type port 8080 ( i.e. I can access > > http://localhost/examples/servlets/index.html. However, whenever I > > try to execute a servlet or JSP it hangs indefinitely. The only > > errors appear in my mod_jk.log file: > > > [ ... ] > > [Mon Dec 23 09:52:47 2002] [jk_connect.c (203)]: jk_open_socket, > > connect() failed errno = 110 [Mon Dec 23 09:52:47 2002] > > [jk_ajp_common.c (626)]: Error connecting to tomcat. Tomcat is > > probably not started or is listenning on the wrong port. Failed errno > > = 110 > [ ... ] > > This seems to be the telling message. So is Tomcat started and running? > And what port is it listening on? More completely, what port is Apache > expecting it to listen on and what port is it set to listen on? The former > is set in workers.properties. The latter is set in server.xml, particularly > in the Connector tag for the Ajp connector (because it may be listening on > different ports for different things, here we only care about Ajp). The > default for that is 8009. It's probably best you post both of those files > (i.e. workers.properties and server.xml) so we can see for sure what you > have there. > > You say that Tomcat is listening on port 8080, but that is the default port > for Tomcat's Http Connector (i.e. Tomcat standalone). So I suspect that is > not the relevant info here. > > Milt Epstein > Research Programmer > Integration and Software Engineering (ISE) > Campus Information Technologies and Educational Services (CITES) University > of Illinois at Urbana-Champaign (UIUC) [EMAIL PROTECTED] > > > -- > 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]> > Milt Epstein Research Programmer Integration and Software Engineering (ISE) Campus Information Technologies and Educational Services (CITES) University of Illinois at Urbana-Champaign (UIUC) [EMAIL PROTECTED] -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
