users@glassfish.java.net

Re: Grizzly consumes 100% CPU in SelectorThread.doSelect if client

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?

http://kb.dbatoolz.com/tp/2476.drill_down_to_java_thread_consuming_cpu_on_solaris.html
[Message sent by forum member 'h1d3m3' (h1d3m3)]

http://forums.java.net/jive/thread.jspa?messageID=317725