This display shows three tables:
Current Live shows the total number of threads running in the JVM.
Hi-Track Threads shows the number of theads currently started directly by
Hi-Track Monitor. There should be 'Hi-Track Threads' rows listed in the Hi-Track Threads table.
Peak shows the maximum number of threads running concurrently since the JVM was
started, or since this counter was reset.
Thread Contention Monitoring shows one of three states: NotSupported, Disabled, or
Enabled. The display currently doesn't display any Thread Contention.
CPU Timing also shows one of the same three states. If CPU Timing is enabled
then the following two tables will include a 'Time' field for each thread.
Run Time (mSec) shows the time (in milliSeconds) since this Hi-Track
Monitor application was started.
The Hi-Track and Service threads tables show very similar data.
Name shows the full thread name. This is the same name that is shown in
the Hi-Track logfile within [] (square brackets). The log process will restrict the thread name
to four characters, by taking the first character and the last two characters; so 'Thread-528'
will be shown as [T'28].
State shows the thread state within the JVM. Hi-Track adds an additional
thread state to this display. '*HUNG*' shows a thread that is not responsive and that Hi-Track
is attempting to restart. Hi-Track Monitor should be stopped and restarted if this state
is not cleared.
Time is the total CPU time (in milliSeconds) used by this thread since in
started.
Restarts is only in the 'Hi-Track Threads' table. The main thread monitors
all other Hi-Track threads and will restart any threads that fail. This column shows the number
of restarts for each thread - it should always be zero. The main thread is not monitored and
its row will be blank.
Blocked shows the following details for how the thread is blocked. The
count of the number of times the thread has blocked is shown within [] (square brackets). If
the thread is currently blocked, then the class name of the blocking object is shown. If there
is one thread blocking this thread then that thread name is displayed after a : (colon).
Waiting shows a count for the number of times the thread has been waiting.
Flags shows a number of characters, each character relating to a particular
state for this thread:
main is the thread that is started when the Hi-Track Monitor application is started. It monitors all the other Hi-Track threads and performs general 'housekeeping'.
CHA is the Transport agent - this will be active only when Hi-Track is transporting data to Hitachi Data System.
*CTL are the polling control threads. There are three such threads:
DCTL controls the polling of Hitachi Storage devices;
SCTL controls the polling of SNMP / Fibre Object devices;and
WCTL controls the polling of all other devices - the only current device
in this group is the Hitachi Essential NAS Platform.
These three threads don't perform the actual polling of devices - they control the scheduling
and control of the polling threads. Each set of polling threads is shown directly underneath
each poll control thread. For example, underneath the SNMP poll control thread SCTL, there may be
five SNMP polling threads, named SP00 through SP04.
DP*, SP*, and SW* are the polling threads.
HT0* are the HTTP service threads.
PPOL is the thread that communicates with a primary Hi-Track Monitor (when the current Hi-Track Monitor is acting as a backup monitor for the primary).
CTL* will be fetching log data from an Hitachi Essential NAS platform.
DFF* will be fetching log data from an Hitachi Storage device.
ES1* will be fetching log data from an Hitachi Data Discovery Suite.