On Wednesday 01 August 2012 10:07:15 Andrew Melo wrote: > 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?
jstack is part of JDK you can see the stack trace via Jenkins UI navigating to $JENKINS_URL/threadDump but not sure if your (or any) Jenkins version provides thread IDs. Once you identify the offending thread, it should be obvious what it does (but it may not be obvious why it does what it does:-)
