Hi, I have a case that CLOSING state socket remains.
And I wonder if this could have led to long latency in Jetty. For example, as more and more CLOSING state sockets get piled up, and reaches to maxThreads, then new requests won't get processed until they are cleaned up. So, when does a Jetty thread become idle, exactly? If it is soon after sending FIN, CLOSING state won't be an issue. I have looked through the source code, also like bug 364921, but didn't get any clue. Can you suggest where to look at? My environment: Jetty8.1 JDK6 SslSelectChannelConnector Thanks! Takenori
_______________________________________________ jetty-users mailing list [email protected] https://dev.eclipse.org/mailman/listinfo/jetty-users
