From: <glassfish_at_javadesktop.org>
Date: Wed, 19 Nov 2008 14:42:52 PST > com.sun.enterprise.web.connector.grizzly.LinkedListPip
> eline for one.
>
> How to proceed? How to identify what class/thread is
> responsible for the cpu behavior?
> Thanks.
I have a lot of those pipeline threads as well, but I found the selector thread specifically because it was the top CPU consuming java thread according to prstat. From there I followed the pid into a stack trace which lead me to the above code. What is your top java thread when you see the load climb?