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=44290>. 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=44290 Summary: mod_jk/1.2.26: retry is not useful for an important use case Product: Tomcat 5 Version: 5.5.5 Platform: Other OS/Version: other Status: NEW Severity: normal Priority: P2 Component: Connector:AJP AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] I am running mod_jk/1.2.26 on a front end server talking to a group of tomcats running on solaris boxes at the back end. The other day one of the Solaris boxes froze, leaving the network connection to the switch up. mod_jk failed to notice that the tomcats on this box were down and kept sending requests. We can reproduce this consistently: if we halt the box, mod_jk does not notice that the tomcat is down. On one occasion we waited more than one hour, and still requests were being sent to the dead tomcat. mod_jk has lots of options for setting timeouts, but none of them seem to deal with this use case. On Linux, we can workaround this by setting the mod_jk socket_timeout however this setting is not supported on solaris. It would be nice to offer a workaround on this platform to make failure monitoring useful. -- 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]
