Hi Blaze, the dump is not that helpful :( BTW, do you see the
"GRIZZLY0023:..." message in the log? If not - it has to be different issue.
I see only one busy Grizzly thread, which is running some GWT RPC task, but
there are lots of EJB threads, so it might be one of them. Let's try to
figure out which exactly thread is consuming 100% CPU. I found a blog [1],
which looks useful. Let me know if it works for you. Thanks. WBR, Alexey. [1]
http://code.nomad-labs.com/2010/11/18/identifying-which-java-thread-is-consuming-most-cpu/
--
[Message sent by forum member 'oleksiys']
View Post: http://forums.java.net/node/892403