Hi, On Tue, Jan 14, 2014 at 2:13 PM, Zen Zhong <[email protected]> wrote: > Hi, > > I found there's connections leak in jetty. Environment: CentOS 6 x86_64, JDK > 7u25 x86_64, jetty-9.1.0.
You have 3 stack dumps that look almost the same. Since reads are non blocking, the timer thread was caught at that point in all 3 times. Did you experience 100% CPU usage for 1 core ? Otherwise it can be explained with a really slow client. Method consumedAll() reads from the client, and it always reads something. Had it read 0 bytes, you would have seen a stack dump waiting in blockForContent(). If you can reproduce this problem, can you enable debug logging for HttpInput and HttpInputOverHTTP ? That should tell us what's going on. Thanks ! -- Simone Bordet ---- http://cometd.org http://webtide.com http://intalio.com Developer advice, training, services and support from the Jetty & CometD experts. Intalio, the modern way to build business applications. _______________________________________________ jetty-users mailing list [email protected] https://dev.eclipse.org/mailman/listinfo/jetty-users
