WIXLIB

Chapter 1Key Monitoring and Management Features–Garbage collection statistics–Low memory detection–On-demand deadlock detection–Operating system information java.util.logging.LoggingMXBean: Enables you to retrieve and set logginginformation. Attach: Allows a management agent to be dynamically loaded onto a virtualmachine. JConsole: Provides a programmatic interface to access JConsole such as addinga JConsole plug-in. JTop is an example of a JConsole plug-in that’s available atthe JDK HOME/demo/management/JTop directory.Monitoring and Management ToolsThe Java SE platform provides a graphical monitoring tool called JConsole. JConsoleimplements the JMX API, and enables you to monitor the performance of a Java VMand any instrumented applications. It provides information to help you optimize theperformance.Some of the enhancements in JConsole are as follows: JConsole plug-in support, which allows you to build your own plug-ins to run withJConsole. For example, you can add a custom tab for accessing the MBeans ofthe application. Dynamic attach capability allowing you to connect JConsole to any application thatsupports the Attach API. Enhanced user interface, which makes data more easily accessible. New Overview and VM Summary tabs for a better presentation of generalinformation about your Java VM. HotSpot Diagnostic MBean, which provides an API to request heap dump atruntime and also change the setting of certain VM options. Improved presentation of MBeans to make it easier to access the MBeansoperations and attributes.JConsole is presented in detail in the Using JConsole topic.Other command-line tools are also supplied with the Java SE platform.Java Management Extensions TechnologyThe Java SE platform, release 9 includes the Java Management Extensions (JMX)specification, version 1.4. The JMX API allows you to instrument applications formonitoring and management. A remote method invocation (RMI) connector allows thisinstrumentation to be remotely accessible, for example, using JConsole.See JMX technology documentation in the Java Platform, Standard Edition JavaManagement Extensions Guide.The following sections provide a brief introduction to the main components of the JMXAPI.1-2

Chapter 1Key Monitoring and Management FeaturesWhat Are MBeans?JMX technology MBeans are managed beans, namely Java objects that representresources to be managed. An MBean has a management interface consisting of thefollowing: Named and typed attributes that can be read and written. Named and typed operations that can be invoked. Typed notifications that can be emitted by the MBean.For example, an MBean representing an application's configuration can have attributesrepresenting different configuration parameters, such as a CacheSize. Reading theCacheSize attribute will return the current size of the cache. Writing CacheSize updatesthe size of the cache, potentially changing the behavior of the running application. Anoperation such as save stores the current configuration persistently. The MBean cansend a notification such as ConfigurationChangedNotification when the configurationchanges.MBeans can be standard or dynamic. Standard MBeans are Java objects that conformto design patterns derived from the JavaBeans component model. Dynamic MBeansdefine their management interface at runtime. An additional type of MBean, calledMXBean, is added to the Java platform. A standard MBean exposes the resource to be managed directly through itsattributes and operations. Attributes are exposed through getter and settermethods. Operations are the other methods of the class that are available tomanagers. All these methods are defined statically in the MBean interface and arevisible to a JMX agent through introspection. This method is the moststraightforward way of making a new resource manageable. A dynamic MBean is an MBean that defines its management interface at runtime.For example, a configuration MBean determines the names and types of theattributes that it exposes, by parsing an XML file. An MXBean is a type of MBean that provides a simple way to code an MBean thatreferences only a predefined set of types. In this way, you can ensure that theMBean is usable by any client. It includes remote clients without any requirementthat the client has access to model-specific classes, which represents the types ofyour MBeans. The platform MBeans are all MXBeans.MBean ServerTo be useful, an MBean must be registered in an MBean server. An MBean server is arepository of MBeans. Each MBean is registered with a unique name within the MBeanserver. Usually the only access to the MBeans is through the MBean server. In otherwords, code does not access an MBean directly, but rather accesses the MBean bythe name through the MBean server.The Java SE platform includes a built-in platform MBean server. See Using thePlatform MBean Server and Platform MXBeans.Creating and Registering MBeansThere are two ways to create an MBean. One is to construct a Java object that will bethe MBean, then use the registerMBean method to register it in the MBean server. The1-3

Chapter 1Platform MXBeansother method is to create and register the MBean in a single operation using one of thecreateMBean methods.The registerMBean method is simpler for local use, but cannot be used remotely. ThecreateMBean method can be used remotely, but sometimes requires attention to theclass loading issues. An MBean can perform actions when it is registered in orunregistered from an MBean server if it implements the MBeanRegistration interface.Instrumenting ApplicationsGeneral instructions on how to instrument your applications for management by theJMX API is beyond the scope of this document.Platform MXBeansA platform MXBean is an MBean for monitoring and managing the Java VM, and othercomponents of the Java Runtime Environment (JRE). Each MXBean encapsulates apart of VM functionality such as the class loading system, just-in-time (JIT) compilationsystem, garbage collector, and so on.Table 1-1 lists all the platform MXBeans and the aspect of the VM that they manage.Each platform MXBean has a unique javax.management.ObjectName for registration inthe platform MBean server. A Java VM may have zero, one, or more than oneinstance of each MXBean, depending on its function, as shown in the table.Table 1-1Platform MXBeansInterfacePart of VM ManagedObject NameInstances per VMClassLoadingMXBeanClass loading systemjava.lang:type ClassLoadingOneCompilationMXBeanCompilation systemjava.lang:type CompilationZero or onejava.lang:type GarbageCollector,name collectorNameOne or moreGarbageCollectorMXB Garbage collectoreanLoggingMXBeanLogging systemMemoryManagerMXBean Memory pool(subinterface ofGarbageCollectorMXBean)java.util.logging:t Oneype Loggingjava.lang:typeMemoryManager,name managerNameOne or moreMemoryPoolMXBeanMemoryjava.lang: type MemoryPool,name poolNameOne or moreMemoryMXBeanMemory systemjava.lang:type MemoryOnejava.lang:type OperatingSystemOnejava.lang:type RuntimeOneOperatingSystemMXBe Underlying operatingsystemanRuntimeMXBeanRuntime system1-4

Chapter 1Platform MBean ServerTable 1-1(Cont.) Platform MXBeansInterfacePart of VM ManagedObject NameInstances per VMThreadMXBeanThread systemjava.lang:type ThreadingOneThe details on platform MXBeans (apart from LoggingMXBean) are described in thejava.lang.management API reference. The LoggingMXBean interface is described inthe java.util.logging API reference.Platform MBean ServerThe platform MBean server can be shared by different managed components runningwithin the same Java VM. You can access the platform MBean server with the methodManagementFactory.getPlatformMBeanServer(). The first call to this method creates theplatform MBean server and registers the platform MXBeans using their unique objectnames. Subsequently, this method returns the initially created platform MBeanServerinstance.MXBeans that are created and destroyed dynamically (for example, memory pools andmanagers) will automatically be registered and unregistered in the platform MBeanserver. If the system property javax.management.builder.initial is set, then theplatform MBean server will be created by the specified MBeanServerBuilder parameter.You can use the platform MBean server to register other MBeans besides the platformMXBeans. This enables all MBeans to be published through the same MBean server,and makes network publishing and discovery easier.1-5

2Monitoring and Management Using JMXTechnologyThe Java virtual machine (Java VM) has built-in instrumentation that enables you tomonitor and manage it using the Java Management Extensions (JMX) technology.These built-in management utilities are often referred to as out-of-the-boxmanagement tools for the Java VM. You can also monitor any appropriatelyinstrumented applications using the JMX API.Setting System PropertiesTo enable and configure the ready-to-use JMX agent so that it can monitor andmanage the Java VM, you must set certain system properties when you start the JavaVM. You set a system property on the command line as follows:java -Dproperty value .You can set any number of system properties in this way. If you do not specify a valuefor a management property, then the property is set with its default value. SeeTable 2-1 for the full set of ready-to-use management properties. You can also setsystem properties in a configuration file, as described in the Ready-to-Use Monitoringand Management Properties section.Note:To run the Java VM from the command line, you must add JRE HOME/bin toyour path, where JRE HOME is the directory containing the Java RuntimeEnvironment (JRE) implementation. Alternatively, you can enter the full pathwhen you enter the command.The syntax and the full set of command-line options supported by the Java HotSpotVMs are described in the Java application launcher section of Java Platform, StandardEdition Tools Reference.Enabling the Ready-to-Use ManagementTo monitor a Java platform using the JMX API, you must do the following:1.Enable the

The Java Virtual Machine (Java VM) is instrumented for monitoring and management, enabling built-in (or ready-to-use) management capabilities that can be accessed both remotely and locally. See Monitoring and Management Using JMX Technology and SNMP Monitoring and Management. The Java VM inc