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=43229>. 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=43229 Summary: mod_jk 1.2.25 different fallback behavior on reply_timeout happens between 1.2.23 and 1.2.25 Product: Tomcat 5 Version: Unknown Platform: PC OS/Version: Linux Status: NEW Severity: major Priority: P2 Component: Native:JK AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] mod_jk 1.2.25 comes with JK_REPLY_TIMEOUT as new error status. on 1.2.25, when reply_timeout is happend on getting replies from tomcat, JK_REPLY_TIMEOUT is returned with http error code JK_HTTP_GATEWAY_TIME_OUT(504) at [EMAIL PROTECTED](line 2038,2107) Currently, mod_jk can handle a fallback operation (send a request to another worker) by lb_worker only when http error code is JK_HTTP_SERVER_BUSY. (see [EMAIL PROTECTED](line 1101)) so, handling JK_HTTP_GATEWAY_TIMEOUT with JK_REPLY_TIMEOUT status, the value of rc is always JK_FALSE, and lb_worker doesn't try next one. 1.2.23 can fall back to the next one because of JK_HTTP_SERVER_BUSY is always returned when reply_timeout occurs. my proposal is that when reply_timeout happenes and op->recoverable is set, return JK_HTTP_SERVER_BUSY as a http error code with status JK_REPLY_TIMEOUT instead of JK_HTTP_GATEWAY_TIMEOUT in order to make lb_worker handle the fallback behavior. thanks in advance. -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
