Hi Dan,
We are using apache web server provided along with RHEL.So I believe we are
getting back port fixes.
In the threaddump we are seeing the below long running threads many times.As
mentioned, we are using AJP(with BIO) and tomacat 7.0.52. I wanted to know
if this will cause any issues like system hung over a period of time. Also
we are thinking of NIO protocol instead of BIO for AJP
"ajp-bio-10.181.42.51-9011-exec-112" daemon prio=10 tid=0x00000000161aa000
nid=0x776c runnable [0x00002b23c3c64000]
java.lang.Thread.State: RUNNABLE
at java.net.SocketInputStream.socketRead0(Native Method)
at java.net.SocketInputStream.read(SocketInputStream.java:152)
at java.net.SocketInputStream.read(SocketInputStream.java:122)
at org.apache.coyote.ajp.AjpProcessor.read(AjpProcessor.java:309)
at org.apache.coyote.ajp.AjpProcessor.readMessage(AjpProcessor.java:364)
at org.apache.coyote.ajp.AjpProcessor.process(AjpProcessor.java:121)
at
org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:607)
at
org.apache.tomcat.util.net.JIoEndpoint$SocketProcessor.run(JIoEndpoint.java:313)
- locked <0x00000007b25a5b58> (a
org.apache.tomcat.util.net.SocketWrapper)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:744)
Locked ownable synchronizers:
- <0x00000007b25e7618> (a
java.util.concurrent.ThreadPoolExecutor$Worker)
Regards,
Ravi
--
View this message in context:
http://tomcat.10.x6.nabble.com/AJP-protocol-with-Apache-Tomcat-Version-7-0-52-tp5017650p5017727.html
Sent from the Tomcat - User mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
