[
https://issues.jboss.org/browse/JBAS-9526?page=com.atlassian.jira.plugin....
]
shikhar khanna updated JBAS-9526:
---------------------------------
Description:
High CPU with lots of Waiting threads on JIoEndpoint$Worker on version 5.0.1
- Running a 100 user load test on JBoss 5.0.1.
- Getting High CPU
- Analyzed thread dumps and found almost 50-60% threads are waiting as per below snippet\
Thread Name : http-0.0.0.0-8080-8 State : in Object.wait() Java Stack at
java.lang.Object.wait(Native Method) - waiting on [0x24d875d0] (a
org.apache.tomcat.util.net.JIoEndpoint$Worker) at java.lang.Object.wait(Object.java:485)
at org.apache.tomcat.util.net.JIoEndpoint$Worker.await(JIoEndpoint.java:416) - locked
[0x24d875d0] (a org.apache.tomcat.util.net.JIoEndpoint$Worker) at
org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:442) at
java.lang.Thread.run(Thread.java:662)
High CPU with lots of Waiting threads on JIoEndpoint$Worker on
version 5.0.1
----------------------------------------------------------------------------
Key: JBAS-9526
URL:
https://issues.jboss.org/browse/JBAS-9526
Project: Application Server 3 4 5 and 6
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Reporter: shikhar khanna
High CPU with lots of Waiting threads on JIoEndpoint$Worker on version 5.0.1
- Running a 100 user load test on JBoss 5.0.1.
- Getting High CPU
- Analyzed thread dumps and found almost 50-60% threads are waiting as per below
snippet\
Thread Name : http-0.0.0.0-8080-8 State : in Object.wait() Java Stack at
java.lang.Object.wait(Native Method) - waiting on [0x24d875d0] (a
org.apache.tomcat.util.net.JIoEndpoint$Worker) at java.lang.Object.wait(Object.java:485)
at org.apache.tomcat.util.net.JIoEndpoint$Worker.await(JIoEndpoint.java:416) - locked
[0x24d875d0] (a org.apache.tomcat.util.net.JIoEndpoint$Worker) at
org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:442) at
java.lang.Thread.run(Thread.java:662)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:
http://www.atlassian.com/software/jira