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=36022>. 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=36022 Summary: It is not possible to set property 'recover_time' to a value less then 60 seconds (mod_jk) Product: Tomcat 5 Version: 5.5.9 Platform: Other OS/Version: Linux Status: NEW Severity: normal Priority: P3 Component: Native:JK AssignedTo: tomcat-dev@jakarta.apache.org ReportedBy: [EMAIL PROTECTED] Hi, I've tested it by using the status page and using a test application. I configured a load balancer with 2 workers (tom1 & tom2) (linux, apache 2.0.54, mod_jk 1.2.14, tomcat 5.5.9 and jdk_1.5.0 update 3). I configured the property recover_time with a value of 10 seconds. First, I stop one tomcat instance (tom1). The status page immediately shows that this worker is in error state. Then, i restart this tomcat instance (tom1), wait 10 seconds, and then stop tomcat instance 2 (tom2). In most times my application shows a 503 Service Temporarily Unavailable page. However, it may occur that the application is working properly. The status page as well does not show that within 10 seconds a tomcat instance is recovered fully (in most cases). The status page of mod_jk 1.2.14 offers the user to alter the recovery time. However, using a value less then 60 does *not* affect a change. Is it possible for future versions to allow a recovery time less than 60 seconds ? -- 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]
