DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://issues.apache.org/bugzilla/show_bug.cgi?id=31733>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.
http://issues.apache.org/bugzilla/show_bug.cgi?id=31733 inconsistent error page returned from Apache when tomcat is started inprocess vs outprocess Summary: inconsistent error page returned from Apache when tomcat is started inprocess vs outprocess Product: Tomcat 5 Version: 5.0.24 Platform: All OS/Version: All Status: NEW Severity: Normal Priority: Other Component: Connector:AJP AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] In case of apache/tomcat using socket connection, when apache is up but tomcat is still coming up and a jsp/servlet from tomcat is requested, then the following error status (http status = 503) is returned to the client "Service Temporarily Unavailable. The server is temporarily unable to service your request due to maintenance downtime or capacity problems ...." However, when tomcat is started inprocess (I cannot accomplish this thru apache/tomcat combination . for now, I am using aolserver/tomcat to start inprocess which seems to work), the code in mod_jk2.c under jk2_handler() shows /* In case of error, if service() set a status code, send it back */ /* Else fallback to HTTP_INTERNAL_SERVER_ERROR (500). */ if (s->status != 0) return s->status; else return HTTP_INTERNAL_SERVER_ERROR; this returns http status = 500. Shouldn't the webserver return same error status regardless of what communication (jni, socket, etc ) to tomcat was utilized ? --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
