in/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:
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 believ
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.
>
erver 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]
> S
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 curr
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.