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=36895>. 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=36895 Summary: get_most_suitable_worker is called twice for a single request Product: Tomcat 5 Version: 5.0.28 Platform: PC OS/Version: Linux Status: NEW Severity: normal Priority: P2 Component: Native:JK AssignedTo: tomcat-dev@jakarta.apache.org ReportedBy: [EMAIL PROTECTED] The function get_most_suitable_worker in jk_lb_worker.c is called twice for each request. jk_handler selects the worker returned from the first called function . So loadbalancing is not perfect. ( in mod_jk version 1.2.14 ) Consider we have two loadbalancer workers tomcat1 and tomcat2 . request1 --> jk_handler <-- tomcat1 ( returned from get_most_suitable_worker) <-- tomcat2 ( returned from get_most_suitable_worker) request2 --> jk_handler <-- tomcat1 ( returned from get_most_suitable_worker) <-- tomcat2 ( returned from get_most_suitable_worker) Here jk_handler always selects tomcat1. If we have 3 loadbalancer workers, the sequence will be like this.... request1 --> jk_handler <-- tomcat1 <-- tomcat2 request2 --> jk_handler <-- tomcat3 <-- tomcat1 request3 --> jk_handler <-- tomcat2 <-- tomcat3 Here the loadbalancing sequence will be ... tomcat1,tomcat3,tomcat2,tomcat1..... -- 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]
