Hi, On Wed, Feb 26, 2014 at 11:35 AM, Mikhail Mazursky <[email protected]> wrote: > Hello all, > > after load test of our application (that uses Jetty client for some > functionality) we noticed that CPU is still being consumed 100%. Thread dump > shows us 6 threads with the following stacktrace that eat all cpu: > > "thread_name-166" prio=10 tid=0x00007f42546e1000 nid=0x4f84 runnable > [0x00007f42963e2000] > java.lang.Thread.State: RUNNABLE > at org.eclipse.jetty.http.HttpParser.parseNext(HttpParser.java:1168) > at > org.eclipse.jetty.client.HttpReceiver.parse(HttpReceiver.java:117) > at > org.eclipse.jetty.client.HttpReceiver.receive(HttpReceiver.java:83) > at > org.eclipse.jetty.client.HttpConnection.receive(HttpConnection.java:273) > at > org.eclipse.jetty.client.HttpConnection.onFillable(HttpConnection.java:261) > at > org.eclipse.jetty.io.AbstractConnection$ReadCallback.run(AbstractConnection.java:358) > at > java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) > at > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) > at java.lang.Thread.run(Thread.java:744) > > Locked ownable synchronizers: > - <0x00000006b143ea70> (a > java.util.concurrent.ThreadPoolExecutor$Worker) > > How can we debug it? What can be the cause? Any help is highly apreciated. > > Jetty 9.0.7, Oracle Java 1.7.0_45 x64.
I think this spin was fixed in 9.1.x. Can you please try the staged 9.1.3 ? https://oss.sonatype.org/content/repositories/jetty-1053 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
