tomcat-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Eric B." <>
Subject Re: How to manage Apache error msgs when Tomcat is down?
Date Fri, 07 Sep 2007 18:08:42 GMT
"Christopher Schultz" <> wrote in message
> Hash: SHA1
> Eric,
> Eric B. wrote:
>> I've currently got an apache/tomcat installation using mod_jk to 
>> communicate
>> between the two.  Everything works perfectly.  The only issue I have is 
>> when
>> I am redeploying my application in tomcat, or decide to stop tomcat
>> altogether, is that I have no idea how to configure a proper error page 
>> to
>> be displayed to the user.
> Did you notice that the error message you get has an HTTP status code
> associated with it?
> Apache httpd knows how to send pages other than the stock ones, like this:
> ErrorDocument 500 down.html  - This covers "TC not running", I think
> ErrorDocument 503 down.html  - This covers "app isn't ready yet"

Sorry - I guess I wasn't specific enough.  The HTTP status code that I got 
from Apache was 200 hence the OK.  I assumed that it was probably 200 since 
I was actually able to communicate with Apache itself, even though its 
request to tomcat was unavailable.  Or unless I am missing something in my 
apache configuration to display the correct error page.

If I check the headers sent using Fiddler, I get the following:
HTTP/1.1 200 OK
Date: Fri, 07 Sep 2007 18:04:51 GMT
Server: Apache/2.0.52 (White Box)
Content-Length: 501
Connection: close
Content-Type: text/html; charset=iso-8859-1

However, it is definitely not "OK" b/c my tomcat server is down.

Do I have something foobar'ed in my apache config?  Or is it a problem in my 
mod_jk params?  If it makes any difference, I am running mod_jk v1.2.10 w/ 
Apache 2.0.52.



To start a new topic, e-mail:
To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message