Denise, What version of Tomcat are you using? One thing to remember is that the CoyoteConnector JkHandler in Tomcat 4.1.(7?) up to about 4.1.14 looked into jk2.properties file for its configuration, ignoring the port value specified in server.xml. Then what it did was assume you wanted some particular port value (I thought it was 8009, it may be different), and if that port was in use it would go to the next one. This shifting port value was a royal pain, and this setup also wasn't conducive to using multiple Tomcat instances. So, in about version 4.1.14, Costin changed the JkHandler to honor the values set in server.xml.
Maybe your problem is that sometimes the java-side Coyote connector WAS listening on 8009, sometimes it wasn't. I would move to a later release (4.1.18?) and try again, since in that version what you have in server.xml will work, and you just need to ensure it is in sync with what mod_jk is looking at (workers.properties typically), and that the worker name in that same file is in sync with the JkMount statements. Every time I've gotten all of the "ducks in a row" like this I've gotten it to work. (On NetWare and Windows, at least). Jeff Tulley ([EMAIL PROTECTED]) (801)861-5322 Novell, Inc., the leading provider of Net business solutions http://www.novell.com >>> [EMAIL PROTECTED] 12/23/02 10:41:50 AM >>> Jeff, Wow, this is very strange. You got me curious as well, and I did change it back to "0" (mind you I was very scared to) . Oddly enough, everything still works. I even tried executing some of the examples that I hadn't accessed yet to make sure it wasn't working from classes that were built previously, and it still works like a charm. If it wasn't the connection timeout setting then I haven't a clue what would have made it start working.... Denise Mangano Help Desk Analyst Complus Data Innovations, Inc. -----Original Message----- From: PELOQUIN,JEFFREY (HP-Boise,ex1) [mailto:[EMAIL PROTECTED]] Sent: Monday, December 23, 2002 12:24 PM To: 'Tomcat Users List' Subject: RE: Mod_jk - won't execute jsp or servlets Denise, Since this week I was scheduled to update our HP-UX apache to latest version which does include mod_jk support, I did the install this morning. My installation with tomcat 4.1.18 does work with the default connectionTimeout="0". I would be interested to know if you change it back to 0, if it will still works. Jeff -----Original Message----- From: Denise Mangano [mailto:[EMAIL PROTECTED]] Sent: Monday, December 23, 2002 10:19 AM To: 'Tomcat Users List' Subject: RES: Mod_jk - won't execute jsp or servlets I don't know what else to say.... But YAY!!!!! :-P Milt - it looks like the timeout was what was doing it. Weird thing is - I didn't edit that. Unless I did something by mistake that is the way that it was shipped!! Everything is working great!! I can access all static pages as well as execute all servlets and JSP. I better knock on wood and pray nothing goes wrong to make it stop working ;) Thank you SO MUCH to everyone for all of your help!! I definitely would have been pulling my hair out from the roots if it weren't for this list!! Jerry - where do you stand with your set up? Since we have the same set up would you like me to send you my files now that it is working for me?? Denise Mangano -----Original Message----- From: Milt Epstein [mailto:[EMAIL PROTECTED]] Sent: Monday, December 23, 2002 11:55 AM To: Tomcat Users List Subject: RE: Mod_jk - won't execute jsp or servlets 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]> -- 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]> -- 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]>
