two tomcat one machine
Hello! I am running two tomcat 3.2.2 on one Solaris machine, each of them is bind to one IP Address via the inet parameter. But now it is impossible to shut the down with the standard process by calling org.apache.tomcat.startup.Tomcat -stop because none of them listen to 127.0.0.1 anymore... Has anyone an idea for this ? Bye, Oli Eales germany.net Technik Tel: +49-69-63397411
Re: two tomcat one machine
Reviewed the code a couple weeks ago looking for a similar solution. You can call org.apache.tomcat.startup.StopTomcat directly with -host and -port options. Check the code for more details if you have trouble...the -port option works for me on 3.3.m3. btw - It's possible I was looking at current 3.3 code and not 3.2.2 so YMMV. Best Regards, Jason Koeninger JJ Computer Consulting http://www.jjcc.com On Tue, 3 Jul 2001 14:41:12 +0200 (CEST), [EMAIL PROTECTED] wrote: Hello! I am running two tomcat 3.2.2 on one Solaris machine, each of them is bind to one IP Address via the inet parameter. But now it is impossible to shut the down with the standard process by calling org.apache.tomcat.startup.Tomcat -stop because none of them listen to 127.0.0.1 anymore... Has anyone an idea for this ? Bye, Oli Eales germany.net Technik Tel: +49-69-63397411
RE: two tomcat one machine
I did tried that option with $TOMCAT_HOME/bin/shutdown.sh -host localhost -port 8011 but the connection is still listening. Here's my netstat -an|grep 80 tcp 0 185 127.0.0.1:8011 127.0.0.1:4178 CLOSE (THIS ONE APPEARS AFTER THE SHUTDOWN COMMAND WAS ISSUED) tcp 0 0 127.0.0.0:8012 0.0.0.0:* LISTEN tcp 0 0 127.0.0.0:8011 0.0.0.0:* LISTEN tcp 0 0 127.0.0.0:8009 0.0.0.0:* LISTEN tcp 0 0 127.0.0.0:8007 0.0.0.0:* LISTEN tcp 0 0 0.0.0.0:8080 0.0.0.0:* LISTEN I had 2 additional type Ajp13 connectors on 8011 8012. I am trying to close 8011. An access to the web server still reveals getting a connection from 8011. Environment: Sun JDK1.3 RHat 7.1 Apache 1.3.20 Tomcat 3.3-m4 Thanks. -keng wong -Original Message- From: Jason Koeninger [mailto:[EMAIL PROTECTED]] Sent: Tuesday, July 03, 2001 7:15 AM To: [EMAIL PROTECTED] Subject: Re: two tomcat one machine Reviewed the code a couple weeks ago looking for a similar solution. You can call org.apache.tomcat.startup.StopTomcat directly with -host and -port options. Check the code for more details if you have trouble...the -port option works for me on 3.3.m3. btw - It's possible I was looking at current 3.3 code and not 3.2.2 so YMMV. Best Regards, Jason Koeninger JJ Computer Consulting http://www.jjcc.com On Tue, 3 Jul 2001 14:41:12 +0200 (CEST), [EMAIL PROTECTED] wrote: Hello! I am running two tomcat 3.2.2 on one Solaris machine, each of them is bind to one IP Address via the inet parameter. But now it is impossible to shut the down with the standard process by calling org.apache.tomcat.startup.Tomcat -stop because none of them listen to 127.0.0.1 anymore... Has anyone an idea for this ? Bye, Oli Eales germany.net Technik Tel: +49-69-63397411
RE: two tomcat one machine
I don't believe ajp13 supports the shutdown commands that Tomcat sends. You should be sending those to an ajp12 port. If you don't have ajp12 running, ps and kill might come in handy. Best Regards, Jason Koeninger JJ Computer Consulting http://www.jjcc.com On Tue, 3 Jul 2001 14:59:57 -0700, Keng Wong wrote: I did tried that option with $TOMCAT_HOME/bin/shutdown.sh -host localhost -port 8011 but the connection is still listening. Here's my netstat -an|grep 80 tcp 0 185 127.0.0.1:8011 127.0.0.1:4178 CLOSE (THIS ONE APPEARS AFTER THE SHUTDOWN COMMAND WAS ISSUED) tcp 0 0 127.0.0.0:8012 0.0.0.0:* LISTEN tcp 0 0 127.0.0.0:8011 0.0.0.0:* LISTEN tcp 0 0 127.0.0.0:8009 0.0.0.0:* LISTEN tcp 0 0 127.0.0.0:8007 0.0.0.0:* LISTEN tcp 0 0 0.0.0.0:8080 0.0.0.0:* LISTEN I had 2 additional type Ajp13 connectors on 8011 8012. I am trying to close 8011. An access to the web server still reveals getting a connection from 8011. Environment: Sun JDK1.3 RHat 7.1 Apache 1.3.20 Tomcat 3.3-m4 Thanks. -keng wong -Original Message- From: Jason Koeninger [mailto:[EMAIL PROTECTED]] Sent: Tuesday, July 03, 2001 7:15 AM To: [EMAIL PROTECTED] Subject: Re: two tomcat one machine Reviewed the code a couple weeks ago looking for a similar solution. You can call org.apache.tomcat.startup.StopTomcat directly with -host and -port options. Check the code for more details if you have trouble...the -port option works for me on 3.3.m3. btw - It's possible I was looking at current 3.3 code and not 3.2.2 so YMMV. Best Regards, Jason Koeninger JJ Computer Consulting http://www.jjcc.com On Tue, 3 Jul 2001 14:41:12 +0200 (CEST), [EMAIL PROTECTED] wrote: Hello! I am running two tomcat 3.2.2 on one Solaris machine, each of them is bind to one IP Address via the inet parameter. But now it is impossible to shut the down with the standard process by calling org.apache.tomcat.startup.Tomcat -stop because none of them listen to 127.0.0.1 anymore... Has anyone an idea for this ? Bye, Oli Eales germany.net Technik Tel: +49-69-63397411
RE: two tomcat one machine
So it looks like I will need to use ajp12 for my loadbalanced workers rather than ajp13 to work (that is to allow shutdowns of certain workers instead of all the workers on the same host) or I will need to shutdown all workers for a particular loadbalanced host with the ./bin/shutdown.sh command (which is the norm anyway). Thanks. -keng wong -Original Message- From: Jason Koeninger [mailto:[EMAIL PROTECTED]] Sent: Tuesday, July 03, 2001 3:03 PM To: [EMAIL PROTECTED]; Keng Wong Subject: RE: two tomcat one machine I don't believe ajp13 supports the shutdown commands that Tomcat sends. You should be sending those to an ajp12 port. If you don't have ajp12 running, ps and kill might come in handy. Best Regards, Jason Koeninger JJ Computer Consulting http://www.jjcc.com On Tue, 3 Jul 2001 14:59:57 -0700, Keng Wong wrote: I did tried that option with $TOMCAT_HOME/bin/shutdown.sh -host localhost -port 8011 but the connection is still listening. Here's my netstat -an|grep 80 tcp 0 185 127.0.0.1:8011 127.0.0.1:4178 CLOSE (THIS ONE APPEARS AFTER THE SHUTDOWN COMMAND WAS ISSUED) tcp 0 0 127.0.0.0:8012 0.0.0.0:* LISTEN tcp 0 0 127.0.0.0:8011 0.0.0.0:* LISTEN tcp 0 0 127.0.0.0:8009 0.0.0.0:* LISTEN tcp 0 0 127.0.0.0:8007 0.0.0.0:* LISTEN tcp 0 0 0.0.0.0:8080 0.0.0.0:* LISTEN I had 2 additional type Ajp13 connectors on 8011 8012. I am trying to close 8011. An access to the web server still reveals getting a connection from 8011. Environment: Sun JDK1.3 RHat 7.1 Apache 1.3.20 Tomcat 3.3-m4 Thanks. -keng wong -Original Message- From: Jason Koeninger [mailto:[EMAIL PROTECTED]] Sent: Tuesday, July 03, 2001 7:15 AM To: [EMAIL PROTECTED] Subject: Re: two tomcat one machine Reviewed the code a couple weeks ago looking for a similar solution. You can call org.apache.tomcat.startup.StopTomcat directly with -host and -port options. Check the code for more details if you have trouble...the -port option works for me on 3.3.m3. btw - It's possible I was looking at current 3.3 code and not 3.2.2 so YMMV. Best Regards, Jason Koeninger JJ Computer Consulting http://www.jjcc.com On Tue, 3 Jul 2001 14:41:12 +0200 (CEST), [EMAIL PROTECTED] wrote: Hello! I am running two tomcat 3.2.2 on one Solaris machine, each of them is bind to one IP Address via the inet parameter. But now it is impossible to shut the down with the standard process by calling org.apache.tomcat.startup.Tomcat -stop because none of them listen to 127.0.0.1 anymore... Has anyone an idea for this ? Bye, Oli Eales germany.net Technik Tel: +49-69-63397411
RE: two tomcat one machine
Just to clarify, you can still use ajp13 to get the performance advantages, but if you want a clean shutdown of Tomcat, you also need to have ajp12 turned on. Best Regards, Jason Koeninger JJ Computer Consulting http://www.jjcc.com On Tue, 3 Jul 2001 15:17:02 -0700, Keng Wong wrote: So it looks like I will need to use ajp12 for my loadbalanced workers rather than ajp13 to work (that is to allow shutdowns of certain workers instead of all the workers on the same host) or I will need to shutdown all workers for a particular loadbalanced host with the ./bin/shutdown.sh command (which is the norm anyway). Thanks. -keng wong -Original Message- From: Jason Koeninger [mailto:[EMAIL PROTECTED]] Sent: Tuesday, July 03, 2001 3:03 PM To: [EMAIL PROTECTED]; Keng Wong Subject: RE: two tomcat one machine I don't believe ajp13 supports the shutdown commands that Tomcat sends. You should be sending those to an ajp12 port. If you don't have ajp12 running, ps and kill might come in handy. Best Regards, Jason Koeninger JJ Computer Consulting http://www.jjcc.com On Tue, 3 Jul 2001 14:59:57 -0700, Keng Wong wrote: I did tried that option with $TOMCAT_HOME/bin/shutdown.sh -host localhost -port 8011 but the connection is still listening. Here's my netstat -an|grep 80 tcp 0 185 127.0.0.1:8011 127.0.0.1:4178 CLOSE (THIS ONE APPEARS AFTER THE SHUTDOWN COMMAND WAS ISSUED) tcp 0 0 127.0.0.0:8012 0.0.0.0:* LISTEN tcp 0 0 127.0.0.0:8011 0.0.0.0:* LISTEN tcp 0 0 127.0.0.0:8009 0.0.0.0:* LISTEN tcp 0 0 127.0.0.0:8007 0.0.0.0:* LISTEN tcp 0 0 0.0.0.0:8080 0.0.0.0:* LISTEN I had 2 additional type Ajp13 connectors on 8011 8012. I am trying to close 8011. An access to the web server still reveals getting a connection from 8011. Environment: Sun JDK1.3 RHat 7.1 Apache 1.3.20 Tomcat 3.3-m4 Thanks. -keng wong -Original Message- From: Jason Koeninger [mailto:[EMAIL PROTECTED]] Sent: Tuesday, July 03, 2001 7:15 AM To: [EMAIL PROTECTED] Subject: Re: two tomcat one machine Reviewed the code a couple weeks ago looking for a similar solution. You can call org.apache.tomcat.startup.StopTomcat directly with -host and -port options. Check the code for more details if you have trouble...the -port option works for me on 3.3.m3. btw - It's possible I was looking at current 3.3 code and not 3.2.2 so YMMV. Best Regards, Jason Koeninger JJ Computer Consulting http://www.jjcc.com On Tue, 3 Jul 2001 14:41:12 +0200 (CEST), [EMAIL PROTECTED] wrote: Hello! I am running two tomcat 3.2.2 on one Solaris machine, each of them is bind to one IP Address via the inet parameter. But now it is impossible to shut the down with the standard process by calling org.apache.tomcat.startup.Tomcat -stop because none of them listen to 127.0.0.1 anymore... Has anyone an idea for this ? Bye, Oli Eales germany.net Technik Tel: +49-69-63397411