tomcat-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Paulsen, Jay M" <jay-paul...@uiowa.edu>
Subject mod_jk error handling question
Date Thu, 16 Dec 2004 00:32:43 GMT
Environment:
Apache 2.0.52
mod_jk 1.2.7-beta-2
Tomcat 5.5.4

I've set up Tomcat with and AJP1.3 Connector to handle requests for web
apps from Apache.  I'd like to be able to set up an ErrorDocument
directive for apache to forward the user to a custom error page when
tomcat is unavailable.  This page would inform the user that maintenance
is being performed on the web app and so on.

When I test this, the http status code that gets returned by mod_jk is
500 (internal server error).  This seems too generic to me as it
encompasses all kinds of other errors that mod_jk could experience.  I
was thinking that mod_jk should return 503 (service unavailable) instead
when tomcat cannot be contacted.

I modified apache-2.0/mod_jk.c (line 1858) to return
HTTP_SERVICE_UNAVAILABLE instead of HTTP_INTERNAL_SERVICE_ERROR.  With
this change mod_jk now returns 503 when tomcat cannot be contacted, but
I have no idea if this is the right place to make this change.  

Is there a better way to handle this or is this an acceptable change?
I'd like to fix it with an Apache source code change as a last resort if
possible.

Any insight is appreciated.


Regards,
Jay 


---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-user-help@jakarta.apache.org


Mime
View raw message