The only real way that I could think to do this (would looking into
the AJP12 and AJP13 specs) is to do a program/script thing that would:
while (true) {
request http://localhost:8080
if request not valid
tomcat start
}
It doesn't seem like it would be all that difficult. Doing it in a
shell script might be a little tricky. (Can you make lynx get only one page
and return an error code if the URL is not responding?)
Just a few thoughts.
Randy
-----Original Message-----
From: Dennis Doubleday [mailto:[EMAIL PROTECTED]]
Sent: Thursday, February 01, 2001 3:57 PM
To: [EMAIL PROTECTED]
Subject: RE: Why use apache
At 03:06 PM 2/1/01, you wrote:
> So, the answer is it really depends. Look at your usage patterns
-
>if its almost exclusively Tomcat-served dynamic content then go with just
>Tomcat. If its mostly static with a few dynamic pages the go with Apache
>and Tomcat. If its in between, experiment and test to determine what's
best
>for your application.
My Apache/Jserv app serves only dynamic requests, but I continue to front
it with Apache because Apache will restart Jserv if it dies (if started in
automatic mode.) I have thought of switching to Tomcat standalone, but is
there a way to replace that restart-on-failure feature?
-------------------------------------------------------------
Dennis Doubleday email: [EMAIL PROTECTED]
yourfit.com, Inc. web: http://www.yourfit.com/
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]
