Jeff, On Wed, Dec 19, 2012 at 6:40 PM, Jeff Segal <[email protected]> wrote: > Yes, they all seem to be waiting on the same lock. Here's a snippet of one > of those threads: > > "qtp1870207216-62" prio=10 tid=0x00007fa36030f800 nid=0x791c waiting for > monitor entry [0x00007fa34a6e9000] > 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)
You need to find the thread that locks, not the ones that are waiting for the lock. Simon -- http://cometd.org http://webtide.com 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 _______________________________________________ jetty-users mailing list [email protected] https://dev.eclipse.org/mailman/listinfo/jetty-users
