jmx-1_2_1-ri.zip

# # @(#)file RELEASE_NOTES.txt # @(#)author Sun Microsystems, Inc. # @(#)version 1.17 # @(#)lastedit 03/08/22 # # Copyright 2003 Sun Microsystems, Inc. All rights reserved. # Use is subject to license terms. # --------------------------------------------------------------------------- Java(TM) Management Extensions (JMX(TM)) 1.2.1 Release Notes --------------------------------------------------------------------------- These Release Notes contain important product notes and list known restrictions in Java Management Extensions (JMX) 1.2.1. Details of workarounds to known bugs are given where possible. In cases where there are differences between these Release Notes and the JMX documentation, the information in these Release Notes supersedes that in the documentation. Contents ~~~~~~~~ 1) JMX 1.2.1 Release Information I. Description II. Operating Environment III. Product Restrictions 2) JMX 1.2 Release Information I. JMX Tracing II. Product Notes III. Product Restrictions 1) JMX 1.2.1 Release Information ================================== I. Description ~~~~~~~~~~~~~~~ Version 1.2.1 of the JMX Reference Implementation is an update of version 1.2, which provides some important bug fixes. It also implements the Errata for the 1.2 Maintenance Release of the Specification, which were published in July 2003. The changes between versions 1.2 and 1.2.1 of the JMX Reference Implementation, as defined by the Errata, are as follows: - Class loader repository can now contain additional class loaders - Illegal identifiers no longer produce exceptions - Notification source rewriting has been clarified - Inconsistency between the specification document, the API documentation, and the RI regarding currencyTimeLimit has been limited - Severity values for ModelMBeanNotificationInfo have been clarified - Optional Model MBean fields have been clarified - API documentation for getDomains() method of MBeanServer interface corrected - Excessive type constraints have been removed from the relation service documentation For more information about these changes, see the document "Errata for JMX Specification, version 1.2" (2003/07/02), which is downloadable from http://jcp.org/aboutJava/communityprocess/final/jsr003/index3.html Note that the JMX API Javadoc bundled with this Reference Implementation reflects the Errata, and hence differs slightly from the Javadoc in the JMX 1.2 Specification. II. Operating Environment ~~~~~~~~~~~~~~~~~~~~~~~~~~ The binary package was built using J2SE 1.4.2 (build 1.4.2-b28). Testing was performed on the following platforms: - Solaris 9 operating environment, SPARC processor, with J2SE 1.3.1 and J2SE 1.4.2. - Redhat Linux 9, with J2SE 1.4.2. - Windows 2000 Professional Edition, with J2SE 1.4.2. III. Product Restrictions ~~~~~~~~~~~~~~~~~~~~~~~~~ The following is a list of known restrictions in this release. 1) BugID 4909536 The MBean server's introspection code, which analyses Standard MBean interfaces to convert them into attributes and operations, will keep a reference to the last class introspected even after the introspection is completed. Therefore, the class and its class loader cannot be garbage collected. 2) JMX 1.2 Release Information ================================ The following information is directly extracted from the release notes that accompanied version 1.2 of the JMX Reference Implementation. I. JMX Tracing ~~~~~~~~~~~~~~ Traces in the JMX implementation are based on the J2SE logging capability (provided by classes in the java.util.logging package). The JMX implementation uses a set of Loggers for sending traces. All Loggers are contained in the javax.management namespace, which corresponds to the name of the root package hosting all public JMX interfaces. The list below shows the Logger objects used in this implementation and their corresponding category of activity. Logger Name Information Logged ----------- ------------------ javax.management.mbeanserver Information about the MBean Server javax.management.mlet Information from an MLet service javax.management.monitor Information from a monitor javax.management.timer Information from a timer javax.management.notification Information from the notification mechanism javax.management.relation Information from the Relation Service javax.management.modelmbean Information from the Model MBean components javax.management.misc Information sent from any other class The following log levels are used in JMX: JMX log level Description ------------- ----------- Level.FINEST Used to print debugging traces (useful for diagnosing the JMX implementation) Level.FINER Used to print information traces Level.SEVERE Used to notify of error conditions NOTE: The JMX 1.2 tracing facility is based on java.util.logging, which is only available in J2SE 1.4. The JMX 1.2 tracing facility can still be run with earlier versions of the JDK (1.3), but in this case the JMX traces will run in a deprecated mode, and will not be available by default. Using JMX Trace with JDK 1.3 ---------------------------- When running the JMX technology on JDK 1.3, you can still get the traces by using a Sun proprietary API: com.sun.jmx.trace.TraceTags defines 3 level of traces: com.sun.jmx.trace.TraceTags.LEVEL_ERROR com.sun.jmx.trace.TraceTags.LEVEL_TRACE com.sun.jmx.trace.TraceTags.LEVEL_DEBUG com.sun.jmx.trace.TraceImplementation defines a destination for JMX traces that can be controlled by two system properties: com.sun.jmx.trace.level=ERROR|TRACE|DEBUG (default is ERROR) lets you define the trace level. com.sun.jmx.trace.file=<filename> lets you define a file in which the traces should be written. If this property is not defined, the traces, when switched on, will be printed on System.err. To switch on the traces, you need to: * Set the com.sun.jmx.trace.level and/or com.sun.jmx.trace.file properties if you want to override the default settings. You can set these properties either by using the System.setProperty(), method or by specifying their value at the Java command line. * call one of the two following static methods: - com.sun.jmx.trace.TraceImplementation.init(); activates the traces using the com.sun.jmx.trace.level and com.sun.jmx.trace.file properties. - com.sun.jmx.trace.TraceImplementation.init(int level); Switch on the traces using the com.sun.jmx.trace.file property, with the given 'level'. Level must be one of: com.sun.jmx.trace.TraceTags.LEVEL_ERROR com.sun.jmx.trace.TraceTags.LEVEL_TRACE com.sun.jmx.trace.TraceTags.LEVEL_DEBUG II. Product Notes ~~~~~~~~~~~~~~~~~ The following are the major issues addressed in the JMX Specification maintenance release, v1.2: 1) New MBeanServer Superinterface The MBeanServer interface in JMX 1.1 was not suitable for exposure to remote clients because it contained methods only appropriate for the exporter of the instrumentation and because it did not declare an appropriate exception for communication failures. A new parent interface, javax.management.MBeanServerConnection, has been added. 2) New removeNotificationListener Methods MBeanServer.removeNotificationListen