You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tomcat.apache.org by yh...@mimic.onesourcecorp.com on 2000/07/06 05:05:05 UTC

Load balancing broken in 3.2b ?

Hi guys,
ive been try the pre release 3.2 which is now on the main webpage...i used
to run tomcat 3.1 with mod_jserv.so and stock redhat 6.2 (kernel upgrade
to 2.2.16-3, suns jdk 1.2.2). with 3.1, i could load balance fine (4
seperate jvms) and simulating heavy loads worked fine. when i tried tomcat
3.2pre the load balancing works ok, but putting it under simulated heavy
loads (3 or more connections per JVM spaced within 10ms of each other
hitting servlets which typically require a second or so of processing time
and around 2 seconds of heavy database work via the mysql jdbc type 4
driver) locks up the JVMs eventually. no errors are reported, however the
lockups seem to be permanent with the jvms chewing up 99% of the CPU and
2% of the memory....typically a non locked up JVM would use 40-50% of the
CPU for 2 seconds and then mysql would show 30% of cpu usage and then both
would go to 0.1%.....mod_jserv.log shows the requests being made..the
servlets start executing and never complete. This only occurs on
3.2pre....3.1 worked fine.
Can anyone help ? i think it should be easy to simulate..just put 4 JVMs
on your machine and put a servlet that loops for 2-3 seconds and prints
something when complete. hit the machine with multiple netscape sessions
and you should see this effect. 
Thanks. 
-Ys-
yhs@mimic.onesourcecorp.com