JBoss is unresponsive because the JBossWeb pool is exhausted in socketRead states

Issue

• JBoss becomes unresponsive and thread dumps show the JBossWeb thread pool is at its max with most threads in a socketRead as seen below:
• Sample http thread stack trace:

"http-127.0.0.1-8080-200" daemon prio=10 tid=0x00007f85fc017000 nid=0x22a5 runnable [0x00007f867df9c000]
   java.lang.Thread.State: RUNNABLE
    at java.net.SocketInputStream.socketRead0(Native Method)
    at java.net.SocketInputStream.read(SocketInputStream.java:146)
    at org.apache.coyote.http11.InternalInputBuffer.fill(InternalInputBuffer.java:729)
    at org.apache.coyote.http11.InternalInputBuffer.parseRequestLine(InternalInputBuffer.java:366)
    at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:790)
    at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:599)
    at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:451)
    at java.lang.Thread.run(Thread.java:636)

• Sample AJP thread stack trace:

"ajp-/0.0.0.0:8109-721" daemon prio=10 tid=0x00007f2450bb4000 nid=0x68f4 runnable [0x00007f2421b91000]
   java.lang.Thread.State: RUNNABLE
    at java.net.SocketInputStream.socketRead0(Native Method)
    at java.net.SocketInputStream.read(SocketInputStream.java:150)
    at java.net.SocketInputStream.read(SocketInputStream.java:121)
    at org.apache.coyote.ajp.AjpProcessor.read(AjpProcessor.java:1131)
    at org.apache.coyote.ajp.AjpProcessor.readMessage(AjpProcessor.java:1213)
    at org.apache.coyote.ajp.AjpProcessor.process(AjpProcessor.java:451)
    at org.apache.coyote.ajp.AjpProtocol$AjpConnectionHandler.process(AjpProtocol.java:452)
    at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:931)
    at java.lang.Thread.run(Thread.java:722)