Java Profiler 9.0 (EAP) HelpProbes: extendable profiling and monitoringBuilt-in probescom.yourkit.probes.builtin.ThreadsThis is a pre-release software documentation. It may be incomplete or not up-to-date.
Description
Probes to monitor some aspects of thread life cycle:
-
where (frame/thread) and when thread objects (instances of
java.lang.Threador its subclass) are created -
where (frame/thread) and when threads are started (
Thread.start()invoked) -
where (frame/thread) and when thread name is changed (
Thread.setName()invoked)
Results are shown in "Probes", table "Thread Life Cycle".
Problem detection: threads created but not started
The table rows represent lasting events. The event starts when thread object is created, and ends when thread is started.
Thus, non-closed events in the table correspond to threads which has not started.
Such threads indicate potential design flaw.
However, note that threads actually started in native code can be shown as not started,
because their start() method is not called.
Problem detection: thread naming issues
Sort by name column to see threads named Thread-<number>.
Such names are given by default if thread name has not been explicitly specified.
Group by name column and sort by row count to see threads with same names.
If either of the problems found, consider better thread naming to improve maintainability and clearness of your application.
Source code location
<Profiler Installation Directory>/probes/src