Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [jetty-users] Load testing slowness


On Wed, Dec 19, 2012 at 3:46 PM, Jeff Segal <jeffrey.segal@xxxxxxxxx> wrote:
> I am load testing a Cometd app deployed to Jetty 8.1.3.v20120416. What I
> find occasionally, but not always, is that the handshake process is
> extremely slow (~15-20s per client instead of 100ms).
> Looking at a thread dump, I see that the vast majority of QTP threads in the
> following state:
> "qtp1870207216-70" prio=10 tid=0x00007fa35419b800 nid=0x7924 waiting for
> monitor entry [0x00007fa349fe2000]
>    java.lang.Thread.State: BLOCKED (on object monitor)
>         at
> org.eclipse.jetty.servlet.ServletHolder.handle(
>         - waiting to lock <0x0000000780398e50> (a
> org.eclipse.jetty.servlet.ServletHolder)

>From the stack trace dump, you should find a stack trace that says
something like:

"locked <0x0000000780398e50>"

What is that thread doing ?

All threads are blocked waiting for the same lock ?

Developer advice, training, services and support
from the Jetty & CometD experts.
Finally, no matter how good the architecture and design are,
to deliver bug-free software with optimal performance and reliability,
the implementation technique must be flawless.   Victoria Livschitz

Back to the top