Yes that would be a good one to attach. It shows locks on things like:
Thread "httpWorkerThread-80-37" thread-id 259 thread-stateBLOCKEDWaiting on lock: com.sun.enterprise.resource.SJSASResourcePool_at_1188708
Owned by: httpWorkerThread-80-0 Id: 93 at: com.sun.enterprise.resource.AbstractResourcePool.getResourceFromPool(AbstractResourcePool.java:752)
Thread "httpWorkerThread-80-38" thread-id 260 thread-stateBLOCKEDWaiting on lock: com.sun.enterprise.server.logging.SystemOutandErrHandler$LoggingPrintStream_at_
Owned by: httpWorkerThread-80-8 Id: 202 at: java.io.PrintStream.println(PrintStream.java:756)
Thread "httpWorkerThread-80-39" thread-id 261 thread-stateBLOCKEDWaiting on lock: org.apache.jasper.servlet.JspServletWrapper_at_2d636d
Owned by: httpWorkerThread-80-28 Id: 250 at: org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:341)
Ryan
glassfish_at_javadesktop.org wrote:
> Ryan,
>
> Thanks for that.. I saw you had done it before, and the responses you got...
>
> I was using openload to build up the load on the server to try and get an increase in speed, and have increased the acceptor threads to 20, and the thread count to 50. I found this increased the speed on the site when under high load (50 - 100 simultaneous connections).
>
> I left this running at 50 connections for 360 seconds (after the server had been running for an hour or so) and it crashed within 300....
>
> The JStack, and thread reports are attached to this thread. It shows blocking threads. Would it be worth attaching this as well?
>
> Thanks,
> Adam
> [Message sent by forum member 'adamburrett' (adamburrett)]
>
> http://forums.java.net/jive/thread.jspa?messageID=278943
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe_at_glassfish.dev.java.net
> For additional commands, e-mail: users-help_at_glassfish.dev.java.net
>
>
>