On Wed, Aug 1, 2012 at 9:48 AM, Vojtech Juranek <vjura...@redhat.com> wrote: > quick way how to look what the thread consuming CPU is doing is to do thread > dump (e.g. using jstack $PID) and use top with threads on (H option) and then > look up, see e.g. > http://code.nomad-labs.com/2010/11/18/identifying-which-java-thread-is- > consuming-most-cpu/
I see. I apparently don't have jstack on this machine :/. Does it only come with the JDK, or can I find it somewhere on the JRE? Once I find the offending thread, should it be pretty obvious what it does? > > On Wednesday 01 August 2012 09:25:08 Andrew Melo wrote: >> On Tue, Jul 31, 2012 at 2:54 PM, Les Mikesell <lesmikes...@gmail.com> wrote: >> > On Tue, Jul 31, 2012 at 2:38 PM, Andrew Melo <andrew.m...@gmail.com> > wrote: >> >>> But if it happened before June 30th or the system has been rebooted >> >>> since, this is not the problem. >> >> >> >> Well, and it's only when i'm using the web interface (or if background >> >> stuff is happening) >> > >> > It affects the linux futex() system call that is used mostly in >> > threaded applications (so you see it in java). And I think it is >> > sort of a race condition where the extra CPU use happens at random. >> >> Well, I restarted it and reset the date and it didn't seem to help. >> I'm pretty helpless when it comes to java, but is there some sort of >> way I can attach a profiler to the process and see what it spins on? >> >> Thanks >> >> > -- >> > >> > Les Mikesell >> > >> > lesmikes...@gmail.com -- -- Andrew Melo
