Limited supportBMC provides limited support for this version of the product. As a result, BMC no longer accepts comments in this space. If you encounter problems with the product version or the space, contact BMC Support.BMC recommends upgrading to the latest version of the product. To see documentation for that version, see BMC AMI Ops Monitor for Java Environments 4.1.

Usage data (JMX) views

The usage data views contain current data for a selected JMX target.

Important

The hyperlinks are available only when the context has a defined JMX port for the JVM. For more information, see Changing-the-context-to-view-JMX-data-for-a-JVM-target.

You can access these views under Usage data (JMX) on the EZJE menu.

View name

Description

Access from

JMX Memory Summary (MEMSUM)

Summarizes JVM memory usage data for each JMX port that is defined to a target.

JVM memory consists of heap and non-heap memory:

  • Heap memory is the runtime data area from which memory for all class instances and arrays is allocated. Heap memory is created at JVM startup. The garbage collector reclaims heap memory for objects.
  • Non-heap memory is for the method area and is created at JVM startup. Non-heap memory stores per-class structures such as a runtime constant pool, field and method data, and code and constructors. In addition to the method area, non-heap memory also includes memory for internal processing or optimization (that is, JIT, native code).

You can hyperlink on the Interval Time and Date column to display data for a selected interval.

You can also hyperlink on the Process ID column to see addition information in BMC AMI Ops Monitor for UNIX System Services views, and on the JMX Port column to see addition information in BMC AMI Ops Monitor for IP views.

Memory Summary option on EZJE

JMX Memory Summary Detail (MEMSUMD)

Displays detailed memory summary information for a selected JVM, including, changes in used memory and CPU time spent doing garbage collection

The view shows values for the interval and the time between requests for data. 

On MEMSUM, hyperlink on the Job Name column.

Memory Manager Summary (MEMMGRZ)

Summarizes memory pools by memory manager and process ID (PID)

Memory Managers option on EZJE

Memory Manager (MEMMGR)

Lists all memory pools managed by memory managers for the JMX targets for the selected service point

On MEMMGRZ, hyperlink on the Memory Manager Name column.

Memory Manager Detail (MEMMGRD)

Displays detailed memory information for a selected memory pool

On MEMMGR, hyperlink on the Pool Name column.

Memory Pools (MEMPOOL)

Displays information about all memory pools associated with the selected memory manager

You can hyperlink on the Interval Time and Date column to display data for a selected interval.

Memory Pools option on EZJE

Memory Pool Detail (MEMPOOLD)

Displays detailed information about a selected memory pool

On MEMPOOL, hyperlink on the Job Name column.

JMX Garbage Collection Summary (GCSUMZ)

Summarizes garbage-collection information by Job name and PID

Garbage Collection option on EZJE

JMX Garbage Collection (GCSUM)

Displays garbage-collection information

On GCSUMZ, hyperlink on the Job Name column.

JMX Garbage Collection interval (GCSUMI)

Displays garbage-collection interval data

Access GCSUMI using one of the following methods:

  • To view garbage-collection interval data for each record in the count, on GCSUMZ hyperlink on the Record Count column.
  • To view garbage-collection interval data for a process ID, on GCSUMZ hyperlink on the Process ID column.

Thread Summary (THRDSUM)

Summarizes detailed thread information for a JVM or JMX port, including:

  • Current number of live threads, live user threads, and live daemon threads
  • Peak number of threads
  • Total number of threads since JVM startup
  • State of a thread (such as runnable, blocked, or waiting)
  • Amount of time that a thread has waited for notification
  • Amount of time that a thread has been blocked
  • Thread lock owner names
  • Line of code where a thread was blocked

In addition, THRDSUM shows whether thread contention is enabled, and whether the JVM supports monitoring of object monitor usage, ownable synchronizer, and thread contention.

Thread Summary option on EZJE

JVM Thread Summary Detail (THRDSUMD)

Displays detailed thread information for a selected JVM

On THRDSUM, hyperlink on the Job Name column.

Thread Detail Summary (THRDDTLZ)

Summarizes of information by thread ID within the JVM

The THRDDTLZ view has one entry for each active thread in the JVM. A stack trace is available for any highlighted thread name.

If a thread is not blocked, BlockObject, LockOwnerName, and LockedAt are null. If thread contention is not supported or disabled, BlockedTime and WaitTime are zero.

For CICS targets, you can hyperlink on the Tran ID, Program Name, and Task Number columns to see additional information about a thread in the BMC AMI Ops Monitor for CICS views.

(BMC.AMIOPS.SPE2110) You can execute the following actions:

  • Temporarily update the stack trace path with the PATh primary command.
  • Request a stack trace for a thread with the TRC line command.

For more information, see Requesting-a-stack-trace-for-a-thread.

On THRDSUM, hyperlink on the Live Curr column.

Thread Detail (THRDDTL)

Displays detailed information about active threads

For CICS targets, you can hyperlink on the Tran ID, Program Name, and Task Number columns to see additional information about a thread in the BMC AMI Ops Monitor for CICS views.

For Db2 threads (com.ibm.db2), you can hyperlink on the Class Name column to see Db2 thread information related to a JVM in BMC AMI Ops Monitor for Db2 views.

Access THRDDTL using one of the following methods:

  • To view information about a specific thread, on THRDDTLZ hyperlink on the Thread State column.
  • To view information about all of the threads that are running in your environment, type THRDDTL on the COMMAND line.

Thread Detail Trace Entry (THRDDTLD)

Displays detailed information about a selected thread

On THRDDTL, hyperlink on the Thread Name column.

Thread Contention (THRDCON)

Displays the status of threads

On the THRDCON view you can identify threads that are in a BLOCKED state. You can hyperlink to the THRDDTLZ view to see details about the thread and the thread lock owner. For more information, see Identifying-blocked-threads.

(BMC.AMIOPS.SPE2110) You can also execute the following actions:

  • Temporarily update the stack trace path with the PATh primary command.
  • Request a stack trace for a thread with the TRC line command.

For more information, see Requesting-a-stack-trace-for-a-thread.

Thread Contention option on EZJE

JVM CPU Usage (JMXCPU)

Displays CPU usage information for each JVM defined in the target profile

The CPU usage consists of the total CPU time in milliseconds for system threads, application threads, and resource-monitor threads.

The system CPU time is an aggregate of GC, JIT, and other daemon threads. The application CPU time can be optionally divided into a maximum of five user-defined categories called Application-User1 through Application-User5.

The Resource-Monitor CPU time is for threads that the application has designated as a resource-monitor category. This CPU time does not count towards determining the state of the application.

JVM CPU Usage option on EZJE

JMX CPU Usage Detail (JMXCPUD)

Displays detailed CPU usage information for a selected JVM

On JMXCPU, hyperlink on the Job Name column.



Related topic

Overview-of-the-EZJE-menu




 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*