More specifics on the versions please. Full version of Jetty, and full version of your JDK. Also, what is your environment OS/Arch?
The connections you are referring to are doing what? Normal servlet? Async servlet? WebSocket? Other? -- Joakim Erdfelt <[email protected]> webtide.com <http://www.webtide.com/> - intalio.com/jetty Expert advice, services and support from from the Jetty & CometD experts eclipse.org/jetty - cometd.org On Thu, Dec 12, 2013 at 7:41 AM, Takenori Sato <[email protected]> wrote: > 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 > >
_______________________________________________ jetty-users mailing list [email protected] https://dev.eclipse.org/mailman/listinfo/jetty-users
