RE: [OT] Mod_jk - won't execute jsp or servlets
My own experience is that if apache comes up before tomcat, you will have an 80% or greater chance of failure and need to do a manual restart of both tomcat and apache. On the flip side, if you have apache and tomcat up and running nicely and do a tomcat restart, I need to restart apache 10% to 15% of the time. An apache restart without a tomcat restart appears to result in a 5% or less failure rate. -Original Message- From: Denise Mangano [mailto:[EMAIL PROTECTED]] Sent: Monday, December 23, 2002 10:50 AM To: 'Tomcat Users List' Subject: RE: [OT] Mod_jk - won't execute jsp or servlets That is definitely a possibility. On average I waited about 10 seconds or so. I usually do ps -ef to make sure tomcat is running, but don't try to pull it up in the browser to see if it really is running. I will keep this checklist for the future. Curious though. Apache is in my startup - Tomcat is not (YET). Will this cause problems if I boot up then start Tomcat? Is it better to remove httpd from startup so I can be sure to start tomcat first? Thanks. 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:43 PM To: 'Tomcat Users List' Subject: RE: Mod_jk - won't execute jsp or servlets I am guessing you had it working at some point in the past but tomcat and apache did not get both get restarted in the right order, Tomcat must be fully up before you start apache A restart scenario we use since tomcat does not always shutdown nicely on HP-UX: stop apache stop tomcat execute ps -ef | grep java to check to make sure Tomcat trully does stop start tomcat wait 30 to 60 sec and/or confirm using your 8080 port that Tomcat is started start apache -Original Message- From: Denise Mangano [mailto:[EMAIL PROTECTED]] Sent: Monday, December 23, 2002 10:42 AM To: 'Tomcat Users List' Subject: RE: Mod_jk - won't execute jsp or servlets 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
RE:[OT] Mod_jk - won't execute jsp or servlets
I am running Tomcat 4.1.17. Funny you mention that because I still see something about jk2.properties in my catalina.out - I had asked what the significance of it was a while back, but I don't believe it was answered (I could be wrong and could have just missed it). This is what shows in my catalina.out log everytime I start Tomcat. Although everything seems to be working fine, I don't understand why the mention of jk2.properties when I am not using it... Dec 23, 2002 3:06:23 PM org.apache.commons.modeler.Registry loadRegistry INFO: Loading registry information Dec 23, 2002 3:06:23 PM org.apache.commons.modeler.Registry getRegistry INFO: Creating new Registry instance Dec 23, 2002 3:06:24 PM org.apache.commons.modeler.Registry getServer INFO: Creating MBeanServer Dec 23, 2002 3:06:25 PM org.apache.coyote.http11.Http11Protocol init INFO: Initializing Coyote HTTP/1.1 on port 8080 Starting service Tomcat-Standalone Apache Tomcat/4.1.17 Dec 23, 2002 3:06:30 PM org.apache.coyote.http11.Http11Protocol start INFO: Starting Coyote HTTP/1.1 on port 8080 Dec 23, 2002 3:06:30 PM org.apache.jk.common.ChannelSocket init INFO: JK2: ajp13 listening on /0.0.0.0:8009 Dec 23, 2002 3:06:30 PM org.apache.jk.server.JkMain start INFO: Jk running ID=0 time=2/46 config=/usr/local/jakarta-tomcat-4.1.17/conf/jk2.properties Denise Mangano Help Desk Analyst Complus Data Innovations, Inc. -Original Message- From: Jeff Tulley [mailto:[EMAIL PROTECTED]] Sent: Monday, December 23, 2002 12:49 PM To: [EMAIL PROTECTED] Subject: RE: Mod_jk - won't execute jsp or servlets 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,
