[jetty-users] Load testing slowness

[Jeff Segal <jeffrey.segal@xxxxxxxxx>]

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(ServletHolder.java:568)

        - waiting to lock <0x0000000780398e50> (a org.eclipse.jetty.servlet.ServletHolder)

        at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1367)

        at org.eclipse.jetty.servlets.CrossOriginFilter.handle(CrossOriginFilter.java:212)

        at org.eclipse.jetty.servlets.CrossOriginFilter.doFilter(CrossOriginFilter.java:179)

        at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1338)

Looking at the source at http://grepcode.com/file/repo1.maven.org/maven2/org.eclipse.jetty/jetty-servlet/8.1.3.v20120416/org/eclipse/jetty/servlet/ServletHolder.java?av=f#568, I see that all of these threads are waiting on the instance of ServletHolder, but I don't see why getServlet() would be running so slow or blocked by a lack of OS resources. But maybe I'm missing something?

Thanks,

Jeff