Posting the update. We had dead FIN_WAIT_2 connections on jetty 7.5.4 and 8.1 snapshot.
Looks like we resolved the problem by installing nginx and configuring it to forward requests to jetty. FYI: We are streaming ActiveMQ messages through HTTP using long pooling. The machine is virtual VMWare server with 2 processors and RAM 4GB. It is running ActiveMQ broker + Jetty with ActiveMQ servlet + Nginx. The server is handling >10K simultaneous sessions. -- View this message in context: http://jetty.1047016.n5.nabble.com/jetty-users-Jetty-8-0-0-8-0-4-not-closing-connections-using-SelectChannelConnector-tp4950273p5019790.html Sent from the jetty-users mailing list archive at Nabble.com. _______________________________________________ jetty-users mailing list [email protected] https://dev.eclipse.org/mailman/listinfo/jetty-users
