View Single Post
  #7 (permalink)  
Old August 14th, 2008, 15:18
acuartero acuartero is offline
Junior Member
 
Join Date: Jul 2006
Posts: 19
Groans: 0
Groaned at 0 Times in 0 Posts
Thanks: 7
Thanked 0 Times in 0 Posts
Rep Power: 0
acuartero is on a distinguished road
Lightbulb Re: Scalability not working as advertised/expected

LenDB2,

I could be wrong but from what I heard the distribution of tasks across the app servers is handled by a stub on the tomcat server (tasks initiated internally such as posting through AQ may arbitrate through other means?). I suspect that since you are posting integration directly to the default app server and not via HTTP POST through the web servers (or via AQ) that you are effectively bypassing the tomcat load balancer code. I also think the design of the load balancer is such that it sends entire tasks to one server or the other and all the threads associated with that task will also reside on that server. It does not take into account factors such as the CPU utilization of the server or the size of the task it simply hands off tasks based on the weight factor you specify.

So the question is are tasks initiated by the users being handed of to the app servers evenly (as you specified equal weights to both) or are all tasks initiated through web connections ending up on your default server. If the latter is the case I suspect that the web servers may be misconfigured.

-Alan
Reply With Quote