Mailing-List: contact users-help@tomcat.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Tomcat Users List" <users@tomcat.apache.org>
Received-SPF: pass (nike.apache.org: domain of jak-tomcat-user@m.gmane.org
 designates 80.91.229.2 as permitted sender)
To: users@tomcat.apache.org
From: "Eric B." <ebenze@hotmail.com>
Subject: Re: How to manage Apache error msgs when Tomcat is down?
Date: Mon, 10 Sep 2007 21:04:24 -0400
Lines: 53
Message-ID: <fc4pis$k8o$1@sea.gmane.org>
References: <fbrr7n$jmc$1@sea.gmane.org>
 <46E1779C.70804@christopherschultz.net> <fbs444$j4e$1@sea.gmane.org>
 <46E2ED85.7040503@kippdata.de>
Sender: news <news@sea.gmane.org>

>> 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.
>
> JK version 1.2.10 is very old. A lot of things changed until we now 
> reached 1.2.25. Typically backend problems will be answered with a non 200 
> status code. Try a more recent version (like 1.2.25).

Thanks for the tip.  I did just that and upgrade to 1.2.19 (I couldn't find
any binaries for 1.2.25 compiled for http 2.0.52 - running CentOS4 and the
latest httpd is 2.0.52-32 - would any binaries later than 1.2.19 work on
that build?), and the status codes are returning properly now.  I get 503
when my tomcat server is down, which made it very easy to then configure
Apache with a standard ErrorDocument 503 msg in httpd.conf.

However, this does raise an interesting question for me now.  I haven't
tried this, so don't know if/how it would work.  If I am mapping an entire
directory in my virtual host - ie: <Virtual Host>JkMount
/tomcat/*</VirtualHost> and my tomcat server is unavailable, it will return
a 503 error status, which httpd will then respond with an appropriate error
document.  Can I customize the error page on a per mount basis by creating a
.htaccess file in my /tomcat/ directory within my httpd file workspace?
Given that httpd is supposed to be ignoring that directory altogether (ie:
passing all requests over to tomcat thru the jk connector), will it even see
/ read the .htaccess file?  If not, do I need to manually add a JkUnmount
/tomcat/.htaccess command?  Or is there a better way to do this to have
apache still read the .htaccess file even if the entire path is mapped to a
jk connector?

Thanks for the info / help!

Eric

(sorry if this is posted multiple times - I seem to be having trouble with 
my relay server) 


---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org