Hi list. There is no way to find out what is going with tomcat and the
CPU reaching 150%. I have been trying to identify the root cause of this
issue. The problem is that with tomcat 6.0.16 the application works very
well, but with tomcat 6.0.29 we get this problem. I updated the JVM from
jdk 1.6.0_05 to jdk 1.6.0_21 and the problem remais. Once the CPU reach
more that 100%, it never comes down unless we restart the container. I
also tried with the APR connector, but the container didnt start up with
this change so i rolledback to Http11NioProtocol (since we are using
comet in our application).
PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
30186 apache 25 0 657m 291m 8112 S 150 14.5 200:47.69 java
3615 apache 15 0 21216 7736 3424 S 0 0.4 0:00.32 httpd
3618 apache 15 0 22056 8548 3400 S 0 0.4 0:00.42 httpd
25181 apache 15 0 20820 7296 3384 S 0 0.4 0:00.25 httpd
25394 apache 15 0 19820 4256 1204 S 0 0.2 0:00.00 httpd
I appreciate if there is anyone else who could give any idea, i ran out
of tries that i could think of. I dont want to go back and use a
previous version other than 6.0.29, but i think i will have no choice.
Thanks
Thiago
*
*
Thiago Locatelli da Silva escreveu:
Hi Chuck, thanks for the reply. I am using CentOS linux with kernel
version 2.6.18-53.1.13.el5.
I have changed the BIO Connector due to our application which makes
use of the comet functionality. This has been a hard time since I need
to make the application work with tomcat 6.0.29 and after some changes
done on the release 6.0.19 the application stopped working.
- Thiago
Caldarale, Charles R escreveu:
From: Thiago Locatelli da Silva [mailto:thiago.si...@digitro.com.br]
Subject: NioBlockingSelector consuming all CPU
I am running tomcat 6.0.29 with jdk 1.6.0_21 (under linux)
Which Linux vendor and version? Others have reported this problem
with a 2.4 kernel, with the problem going away under 2.6.
You could also try the normal BIO connector or APR to see if that
makes a difference.
- Chuck
THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE
PROPRIETARY MATERIAL and is thus for use only by the intended
recipient. If you received this in error, please contact the sender
and delete the e-mail and its attachments from all computers.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org
