I'm curious, what are the issues with loadbalancing in mod_jk with a pre-forking Apache?
Basically it comes down to the fact that the children don't talk to one another, so each one has its own idea of the relative loads. This usually results in a distribution (for the two-Tomcat case) somewhere between 70-30 and 80-20 (although people on this list have reported even more skewed distributions). It should get even more skewed as you increase the number of Tomcats.
mod_jk2 already has the scoreboard (aka shm) in place to allow for the children to coordinate this, but at the moment isn't using it for loadbalancing (and so, is just as broken as mod_jk). I can't add much more except that patches are always welcome ;-)
Thanks, that explains the situation perfectly. Just to be clear, if you are using Apache 2 with threaded workers, threaded workers spawned from the same process do share the loadbalancing information correctly at this time?
-Dave
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
