Is it normal to have many JBoss web connector threads in BLOCKED or IN_NATIVE states?
Issue
Is there anything suspicious in this thread dump? I can see most of them are in BLOCKED and AJP threads are in IN_NATIVE state.
Thread 9213: (state = BLOCKED)
- java.lang.Object.wait(long) @bci=0 (Interpreted frame)
- java.lang.Object.wait() @bci=2, line=485 (Compiled frame)
- org.apache.tomcat.util.net.JIoEndpoint$Worker.await() @bci=8, line=420 (Compiled frame)
- org.apache.tomcat.util.net.JIoEndpoint$Worker.run() @bci=11, line=446 (Interpreted frame)
- java.lang.Thread.run() @bci=11, line=662 (Interpreted frame)
Thread 9212: (state = IN_NATIVE)
- java.net.SocketInputStream.socketRead0(java.io.FileDescriptor, byte[], int, int, int) @bci=0 (Compiled frame; information may be imprecise)
- java.net.SocketInputStream.read(byte[], int, int) @bci=84, line=129 (Compiled frame)
- org.apache.coyote.ajp.AjpProcessor.read(byte[], int, int) @bci=25, line=1036 (Compiled frame)
- org.apache.coyote.ajp.AjpProcessor.readMessage(org.apache.coyote.ajp.AjpMessage) @bci=12, line=1115 (Compiled frame)
- org.apache.coyote.ajp.AjpProcessor.process(java.net.Socket) @bci=87, line=383 (Compiled frame)
- org.apache.coyote.ajp.AjpProtocol$AjpConnectionHandler.process(java.net.Socket) @bci=39, line=385 (Interpreted frame)
- org.apache.tomcat.util.net.JIoEndpoint$Worker.run() @bci=41, line=451 (Interpreted frame)
- java.lang.Thread.run() @bci=11, line=662 (Interpreted frame)
Environment
- JBoss Enterprise Application Platform (EAP) 5, 6
Subscriber exclusive content
A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.
Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.
