I came across your post on the below discussion to monitor hung threads. We are seeing a hung thread situation with a thread consuming high CPU for an application and wanted to utilize the Jtop.zip to identify the thread consuming the max CPU. I followed the instructions in the readme file and configured the extension without any grouping( using the default of none). However I see the Max CPU Thread metric as inactive( grayed out). Can you please guide us on what maybe missing for this metric to not report any stat?
It could depend on OS, hardware, and JRE version. It was compiled for Java 1.5 so if you're using something more recent, it may require a recompile. You can try to reach Jack at his personal email listed in his README.
As Hiko_Davis mentioned, this could be due to a mismatch in Java versions; before I re-compile and re-upload, however, can you give me some specifics about your environment, e.g. operating system, JRE version, processor type?
Also, would you mind adding the below property to your IntroscopeAgent.profile, restarting your instrumented application, and, after restart, sending me the IntroscopeAgent.log?
Please feel free to send me the log privately, rather than posting it publicly here. And if you'd rather not send the entire contents of the log file to me, you could set the overall agent log level as below, delete/rename/move the existing file, and then restart. After the restart completes, only the JTop log messages should be present in the IntroscopeAgent.log:
Thanks Jack for following up!
Retrieving data ...