Hi Alfredo,
It looks like 11 ajp threads are stuck because they are waiting for a response from the external service. Here is a stack trace of thread -
stackTrace: 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:1124) at org.apache.coyote.ajp.AjpProcessor.readMessage(AjpProcessor.java:1206) at org.apache.coyote.ajp.AjpProcessor.process(AjpProcessor.java:438) at org.apache.coyote.ajp.AjpProtocol$AjpConnectionHandler.process(AjpProtocol.java:420) at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:926) at java.lang.Thread.run(Thread.java:745) Locked ownable synchronizers: - None
JDK's java.net layer uses SocketInputStream.socketRead0() API to read and receive the data from the external application. Sometimes your application might not get a response from the external applications. In that case, your application thread will be stuck in this java.net.SocketInputStream.socketRead0() API.
Edit your Comment