Yes, right, that was the mail I meant. Your assumption about "failover instead of load balancing" seems to be correct, at least, at my cluster (one local server, on a remote machine another server + VMWare with a third server) it is the same - thanks for that comment, I was to blind to see it myself. ;-)
I'll try to find out more tomorrow, maybe we'll get it to work - I'd be very interested in your progresses, however. Do you've got any idea how to realise load balancing with a defined distribution? Or, in other words: as long as it does not work properly with Tomcat & mod_jk2, are there any reasons to use those, after all, instead of Tomcat's "balancer"-webapp, if one is mainly interested in performance issues? -----Ursprüngliche Nachricht----- Von: Kommuru, Bhaskar [mailto:[EMAIL PROTECTED] Gesendet: Donnerstag, 17. Juni 2004 16:09 An: 'Tomcat Users List' Betreff: RE: JK2: lb_factor Do you remember that mail about "lb_factor"? What you said it right about lb_factor. Changing this value does not affect easily. -----Original Message----- From: Weseloh, Nicole [mailto:[EMAIL PROTECTED] Sent: Thursday, June 17, 2004 2:39 PM To: Tomcat Users List Subject: AW: JK2: lb_factor Yes, I'm still struggling, too, and have quite similar problems now - I added a third server to the load balanced cluster, but only two of them get requests. I shut down each server in turn, and the load got balanced fine between the remaining two - on starting up the third server again, one always becomes idle (not always the same, above all...). Not talking about the fact that setting lb_factor to whatever value doesn't seem to have much effect on the load distribution... At least, I found out that lb_factor has nothing to do with a "factor", indeed - assume that each worker has an initial "lb_value", set to it's lb_factor. With every request, a worker is chosen, its lb_value gets increased by its lb_factor, and if it's smaller than lb_value of the other nodes, that worker gets the request. If lb_value is > 255, it gets resetted to 0. ^^ Just search archives of Apache User Mailing List, found it there (and hope I understood correctly) - however, the mail was from some months ago, so I really don't know if it still works like this. I'd really like to know if someone has managed to build a cluster of more than 2 Tomcat servers, using Apache + JK2, with working loadbalancing? Just curious... If someone could give a hint why it does such strange things (like "ignoring" cluster nodes), we'd of course be thankful, too... :) Greets, Nicole -----Ursprüngliche Nachricht----- Von: Kommuru, Bhaskar [mailto:[EMAIL PROTECTED] Gesendet: Donnerstag, 17. Juni 2004 14:12 An: 'Tomcat Users List' Betreff: RE: JK2: lb_factor I too have similar problem and have been struggling since morning. My problem is my mod_jk2 doesnt even load balance to remote server. When i shut down local servers, it puts the request to remote server.. no cluesss!! -----Original Message----- From: Weseloh, Nicole [mailto:[EMAIL PROTECTED] Sent: Wednesday, June 16, 2004 11:48 AM To: [EMAIL PROTECTED] Subject: JK2: lb_factor Hello, I've got a cluster with 2 tomcat 2.0.25 on different machines, on one of them also running Apache 2.0.49 with JK2 as a loadbalancer. Requests get redirected to both tomcat instances, but it always ends up with around 1/3 of all requests at the local server and about 2/3 at the remote one, no matter what value the lb_factors are. So, could anyone tell me which values I should use to make the lb_factor work correctly? All information I found was that "a lower value means more requests" (official JK2-documentation at jakarta.apache.org). ===================================== My workers2.properties: [lb:lb] stickySession=1 # First Tomcat Instance (Localhost / 10.32.97.44) [channel.socket:localhost:8009] port=8009 host=127.0.0.1 group=lb lb_factor=1 tomcatId=tomcat01 # Second Tomcat Instance (10.32.97.23) [channel.socket:10.32.97.23:8009] port=8009 host=10.32.97.23 group=lb lb_factor=1 tomcatId=tomcat02 # define the worker for tomcat instance 1 (localhost) [ajp13:localhost:8009] channel=channel.socket:localhost:8009 # define the worker for tomcat instance 2 [ajp13:10.32.97.23:8009] channel=channel.socket:10.32.97.23:8009 #This is the application to test the cluster / load balancing... [uri:/benchmark/*] info=Benchmark application ==================================== Anything wrong with that? Anything missing? If more information needed, just tell me.. I just guessed that the workers2.properties is the problem. Greets, Nicole ------------------------------------------------------------ Diese E-Mail enthalt vertrauliche und/oder rechtlich geschutzte Informationen. Wenn Sie nicht der richtige Adressat sind oder diese E-Mail irrtumlich erhalten haben, informieren Sie bitte sofort den Absender und vernichten Sie diese Mail. Das unerlaubte Kopieren sowie die unbefugte Weitergabe dieser Mail ist nicht gestattet. This e-mail may contain confidential and/or privileged information. If you are not the intended recipient (or have received this e-mail in error) please notify the sender immediately and destroy this e-mail. Any unauthorized copying, disclosure or distribution of the material in this e-mail is strictly forbidden. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] ____________________________________________________________________________ ______________________________________________________ For information about the Standard Bank group visit our web site <www.standardbank.co.za> ____________________________________________________________________________ ______________________________________________________ Disclaimer and confidentiality note Everything in this e-mail and any attachments relating to the official business of Standard Bank Group Limited is proprietary to the group. It is confidential, legally privileged and protected by law. Standard Bank does not own and endorse any other content. Views and opinions are those of the sender unless clearly stated as being that of the group. The person addressed in the e-mail is the sole authorised recipient. Please notify the sender immediately if it has unintentionally reached you and do not read, disclose or use the content in any way. Standard Bank can not assure that the integrity of this communication has been maintained nor that it is free of errors, virus, interception or interference. ____________________________________________________________________________ _______________________________________________________ ------------------------------------------------------------ Diese E-Mail enthält vertrauliche und/oder rechtlich geschützte Informationen. Wenn Sie nicht der richtige Adressat sind oder diese E-Mail irrtümlich erhalten haben, informieren Sie bitte sofort den Absender und vernichten Sie diese Mail. Das unerlaubte Kopieren sowie die unbefugte Weitergabe dieser Mail ist nicht gestattet. This e-mail may contain confidential and/or privileged information. If you are not the intended recipient (or have received this e-mail in error) please notify the sender immediately and destroy this e-mail. Any unauthorized copying, disclosure or distribution of the material in this e-mail is strictly forbidden. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] __________________________________________________________________________________________________________________________________ For information about the Standard Bank group visit our web site <www.standardbank.co.za> __________________________________________________________________________________________________________________________________ Disclaimer and confidentiality note Everything in this e-mail and any attachments relating to the official business of Standard Bank Group Limited is proprietary to the group. It is confidential, legally privileged and protected by law. Standard Bank does not own and endorse any other content. Views and opinions are those of the sender unless clearly stated as being that of the group. The person addressed in the e-mail is the sole authorised recipient. Please notify the sender immediately if it has unintentionally reached you and do not read, disclose or use the content in any way. Standard Bank can not assure that the integrity of this communication has been maintained nor that it is free of errors, virus, interception or interference. ___________________________________________________________________________________________________________________________________ --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
