Hi Jake,
This is a very good question, and I also would like to know the
answer.
In fact, in my company we're testing Jetty using mod_jk2 and
detected a problem with its AJP13 Listener, which is already corrected. But
we're still having some performance problems and connections closing from
nowhere under very heavy load.
In mod_jk2, we detected a problem and I'd like to share with you
all. In the source code file jk_worker_lb.c, lines 277-280, we had to
comment out the following part to make load balancing work:
for(i = 0 ; i < lb->workerCnt[currentLevel] ; i++) {
jk_worker_t *w=lb->workerTables[currentLevel][i];
w->lb_value=w->lb_factor;
}
With this code, it looks like that a overloaded worker would still
receive requests, even if all the others were idle. Could some one please
confirm this to me? Our environment is Linux RH 7.2, Apache 2.0.44, mod_jk2
2.0.2 and Jetty 4.2.8.
We are even considering using mod_jk, if you say mod_jk2 is not
mature enough to put into production.
Does anyone have some comments on this? TIA;
Kraemer
--
Eduardo Kraemer Góes
Systems Engineer
UOL Inc.
> -----Original Message-----
> From: Jake Robb [mailto:[EMAIL PROTECTED]
> Sent: terça-feira, 4 de março de 2003 18:26
> To: Tomcat Users List
> Subject: mod_jk2
>
>
> Is there an easy way to keep tabs on the progress/status of mod_jk2
> development? I'd like to use it, but I'm understandably wary
> about using
> development-quality stuff in a production environment. In
> the little use
> I've given it on my test machine, jk2 has worked well, but I
> can't deploy it
> without some assurance.
>
> Is there a to-do list, or a known issue list, or anything
> like that, which
> would allow me to know whether jk2 is up to the task, and if not, what
> obstacles the jk2 development team still need to tackle in
> order to get it
> there?
>
> Thanks,
> Jake
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
