Chris
Thanks for the response here are the details , i can also see that the
backend tomcat which has high cpu has processed less number of request when
compared with other tomcat's i checked this from tomcat access logs , in
the monotoring tool i can see that the tomcat which has issues have taken
more hits/sec when compared to others
as of now i am suspecting the busyness method has sent more
request to the tomcat that served less number of request's (the tomcat
which has high cpu) , which is unable to serve the requests due to hung
threads to DB
*Tomcat version *
6.0
*Apache Version *
2.2
*Thread dump anylisis*
>From thread dump i can see that most of the threads are waiting on DB ,and
other are mod_jk threads Application uses c3po mchange to connect to DB
worker.propertires
*here is my work.property file*
worker.xxx.type=lb worker.xxx.method=Busyness Definite common values for
all xxxlb workers
*worker.xxxlb.common.type=ajp13 worker.xxxlb.common.lbfactor=1
worker.xxxlb.common.ping_mode=A
worker.xxxlb.common.socket_connect_timeout=10000
worker.xxxlb.common.connection_pool_size=6*
*worker.xxxlb.common.connection_pool_timeout=600
worker.xxxlb.common.socket_keepalive=True*
On Sat, Dec 27, 2014 at 9:31 PM, Christopher Schultz <
ch...@christopherschultz.net> wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA256
>
> Rajesh,
>
> On 12/24/14 7:50 AM, Rajesh Cherukuri wrote:
> > Qe have noticed that mod_jk method busyness is sending more
> > requests to backend tomcat and causing hung threads and high CPU.
> >
> > [I] need to understand why it's doing that.
>
> Are you saying that you are getting N requests to httpd from clients
> and Tomcat is receiving M x N requests where M > 1.0?
>
> That suggests that the Tomcat thread is not returning anything within
> a certain amount of time and mod_jk is re-trying the request on
> another host.
>
> What is your Tomcat version? mod_jk version? httpd version? Can you
> post your mod_jk configuration (everything in workers.properties) and
> tell us about where the threads are stuck on the Tomcat side (take a
> thread dump and look at where the threads are stuck). Are they all
> stuck in the same place?
>
> - -chris
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1
> Comment: GPGTools - http://gpgtools.org
>
> iQIcBAEBCAAGBQJUntfJAAoJEBzwKT+lPKRYtAEQAKZFhibbMepBa5QL3hCeCfwH
> mLpK2OKc5Pr+ErlF0yIHScZr56uM7v6bHyCH3Ut2z+M5E8W+IlSJI13tYewp5dMg
> ccvYh9LLYpWvIl9ZcdKG7MqSHOsF2zqb3FijjYDMBQwgU6onY0oINLDhOl7Led+t
> 3tjxZLig5fHzaBWQ7c04Fp96awIghHHp6N5O/kGv4/aeLV+jHi5uxg9cL5G2LMiW
> ZTKMvdkn8YyAhmJYEGHy6T6Ypba+qsnGsHjUvWPfhb7TTTDPqFgoPPaux5g6XqKM
> 5SP3vOzRmhk+w62IcIPJzh5x/jo60ia/fOTVuRS9IL/UG1B+X9rnGwXupOaeE/jB
> O5FzfLMh6nmqQ2h0QD1if+bd/JojoHABa68bfnJZ6OejHYJ+eHqPrutpRT4A0cQR
> 4mskyQbt1wtTwtmioU9sPqVqJWWlviKa573691uw2HSrQMjOZrD9RFZ/iwzeRowC
> kO7Q2MdkBK1vKhc0xSh2bZsr3hNC+gbABNHE4SoaZRDh48pghC9T7UOjb95tXf0z
> VHYJy05CmWr2dmmF8KOe7Gyri3tGrTKyQ/PtOdz/ppWqz+/co9xbv3kzOxT3W4mz
> 2r5QfYoOAnNd9ank2q0rbVB9sTDQlD0U5NoXhqAOxwulFglrraelMSLUJXML2TEn
> xg50hO7JZj9rYklYV5gF
> =hQzk
> -----END PGP SIGNATURE-----
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
> For additional commands, e-mail: users-h...@tomcat.apache.org
>
>
