Java Management Extensions (JMX ) Technology: Who s Doing What

Transcription

1 Java Management Extensions (JMX ) Technology: Who s Doing What Éamonn McManus JMX Specification Lead Sun Microsystems x Session TS-2656 Jean-François Denise JMX Technology Team Sun Microsystems JavaOne SM Conference Session TS-2656

2 Goals of This Talk Learn what JMX technology is, where it is used, and how you can use it yourself. Learn what changes are planned for future versions of the API JavaOne SM Conference Session TS

3 Agenda Introduction to JMX Technology Some Uses of the Technology Aspect-Oriented Programming Java Specification Requests (JSRs) JSR 255 (JMX API 2.0) JSR 262 (Web Services Connector) 2007 JavaOne SM Conference Session TS

4 Agenda Introduction to JMX Technology Some Uses of the Technology Aspect-Oriented Programming Java Specification Requests (JSRs) JSR 255 (JMX API 2.0) JSR 262 (Web Services Connector) 2007 JavaOne SM Conference Session TS

5 JMX API A standard part of the Java Platform, Standard Edition (Java SE platform) Starting with version 5.0 Also part of Java 2 Platform, Enterprise Edition (J2EE ) 1.4 platform Can be used for management... For example, changing configuration settings...and monitoring... For example, obtaining statistics and error notifications...of running applications From big server applications to embedded device controllers 2007 JavaOne SM Conference Session TS

6 Example: VM Instrumentation As of version 5.0, the Java platform exports lots of monitoring data via JMX technology Number of threads Stack of any given thread Sizes of different memory areas Time spent doing garbage collection Number of classes Class path You can also provoke a garbage collection remotely 2007 JavaOne SM Conference Session TS

7 DEMO VM Instrumentation 2007 JavaOne SM Conference Session TS

8 Example: Phased Upgrade You have a new version of your web commerce app that appears to work, but it hasn t yet been tested live Maybe it will fail catastrophically in live conditions! Solution: initially route only n% of incoming requests to the new version You can use JMX technology to increase n in the live system as you become confident in the new version 2007 JavaOne SM Conference Session TS

9 Adding JMX Instrumentation to Your Application Remote Manager Application JMX Agent Manages 2007 JavaOne SM Conference Session TS

10 MBeans An MBean is a named managed object representing a resource Application configuration setting Program module Device Collection of statistics etc. An MBean can have: Attributes that can be read and/or written Operations that can be invoked Notifications that the MBean can send 2007 JavaOne SM Conference Session TS

11 MBean Example CacheControlMBean Used: int Size: int save(): void dropoldest(int n): int R RW Attributes Operations com.example.config.change com.example.cache.full Notifications 2007 JavaOne SM Conference Session TS

12 DEMO MBean Example CacheControlMBean 2007 JavaOne SM Conference Session TS

13 Standard MBeans There are several kinds of MBeans Standard, MXBean, Dynamic, Model, Open The simplest are Standard MBeans and their cousins, MXBeans To make a Standard MBean: 1.Write a bean interface called SomethingMBean 2.Implement it in a class called Something 3.Then an instance of Something is a Standard MBean 2007 JavaOne SM Conference Session TS

14 Standard MBean Example public interface CacheControlMBean { // a read-write attribute called Size // of type int public int getsize(); public void setsize(int size); // a read-only attribute called Used // of type int public int getused(); } // an operation called dropoldest // with a parameter and a return value public int dropoldest(int n); public class CacheControl implements CacheControlMBean {...} 2007 JavaOne SM Conference Session TS

15 MXBeans A variant of Standard MBeans introduced in the Java SE 6 platform Basically the same as Standard MBeans when all attribute and operation types are simple public interface CacheControlMXBean { public int getused(); public int dropoldest(int n); User-defined JavaBean classes mapped to a set of standard types public interface CacheControlMXBean { public CacheStats getcachestats(); Clients (like JConsole) don t need to know CacheStats, only the standard types 2007 JavaOne SM Conference Session TS

16 MBean Server (JMX Agent) MBean Server CacheControlMBean com.example:type=cachecontrol 2007 JavaOne SM Conference Session TS

17 Registering an MBean public class CacheControl implements CacheControlMBean {...} MBeanServer mbs = ManagementFactory.getPlatformMBeanServer(); CacheControl mbean = new CacheControl(); ObjectName name = new ObjectName("com.example:type=CacheControl"); mbs.registermbean(mbean, name); See online tutorial, or documentation for package javax.management Reminder: JavaOne SM Conference Session TS

18 Making the JMX Agent Connectable How to enable JConsole to connect Java Development Kit (JDK ) version 1.4 Add JMX API jars to the classpath Use JMX remote API to set up connectivity JDK version 5.0 Run your app with system properties such as -Dcom.sun.management.jmxremote JDK version 6 It just works! (If you are connecting from the same machine) You can always use JConsole from a later JDK version to connect to an agent on an earlier one 2007 JavaOne SM Conference Session TS

19 Agenda Introduction to JMX Technology Some Uses of the Technology Aspect-Oriented Programming Java Specification Requests (JSRs) JSR 255 (JMX API 2.0) JSR 262 (Web Services Connector) 2007 JavaOne SM Conference Session TS

20 Who s Doing What All app servers come with JMX technology Mandated since J2EE specification 1.4 App servers all had it before then anyway Numerous open source projects 89 projects on sourceforge.net mention JMX technology About half of them have JMX technology as their principal focus 2007 JavaOne SM Conference Session TS

21 Some Open Source Projects Not to mention the big one: JDK software platform! MX4J A re-implementation of the JMX API, plus some useful classes MC4J A configurable JMX API console built on NetBeans software platform jmanage A web-based MBean browser OpenDMK Sun s Java DMK product open-sourced Includes cascading, discovery 2007 JavaOne SM Conference Session TS

22 Some Commercial Products Many commercial products understand JMX technology Mainly, so they can manage app servers BMC Patrol HP Open View IBM Tivoli SAP CCMS Adventnet Applications Manager This list is not exhaustive! See JMXperience at JavaOne SM Conference Session TS

23 Agenda Introduction to JMX Technology Some Uses of the Technology Aspect-Oriented Programming Java Specification Requests (JSRs) JSR 255 (JMX API 2.0) JSR 262 (Web Services Connector) 2007 JavaOne SM Conference Session TS

24 Glassbox An open source project based on Spring Uses AspectJ to insert timing measurements into arbitrary apps at runtime No code modification needed Exposes measurement results as MBeans A special web app analyzes these results and reports on possible problems 2007 JavaOne SM Conference Session TS

25 DEMO Glassbox 2007 JavaOne SM Conference Session TS

26 Glassbox MBeans 2007 JavaOne SM Conference Session TS

27 Glassbox Analysis 2007 JavaOne SM Conference Session TS

28 Aspect-Oriented Programming Aspect-Oriented Programming (AOP) allows you to cause extra code to be executed at certain points in your program Every time my code calls File.createTempFile, add one to a counter Every time my code gets an exception, log a message Every time a class in com.example.mypackage calls a method in java.net, print a stack trace 2007 JavaOne SM Conference Session TS

29 AOP Vocabulary AOP terminology seems to have been designed to be as cryptic as possible join points, pointcuts, advice, aspects We will explain the jargon where relevant, then avoid using it 2007 JavaOne SM Conference Session TS

30 Pointcuts AOP gives you a language to describe points of interest in your program A call to File.createTempFile A call to any method in java.io.file A call to File.createTempFile from code in com.example.mypackage and where the second argument is not null Construction of any object from within the class com.example.mypackage.myclass These are pointcuts A pointcut is a set of join points, but you don t care 2007 JavaOne SM Conference Session TS

31 Advice Once you have specified what points in the execution of the program are of interest, you can say what you want to happen Before After Around Before every call to File.createTempFile, increment this counter Around every call to Socket.connect, measure the time taken This is called advice, for some reason 2007 JavaOne SM Conference Session TS

32 Proceed With Caution 2007 JavaOne SM Conference Session TS

33 Evil AOP Warning: subjectivity You can inject any code into any method in your application This injected code can change what the method does So what you see is no longer what you get This can destroy one of the big advantages of the Java programming language, its transparency We will describe ways to inject code that observes what is going on, but does not change it 2007 JavaOne SM Conference Session TS

34 AspectJ (1) AspectJ is an extension of the Java programming language that adds AOP constructs before(): call(* java.io.file.createtempfile(..)) { tempfilestats.addcall(); is a set of annotations you can use in a normal Java platform program to the same java.io.file.createtempfile(..))") public void updatetempfilestats() { tempfilestats.addcall(); } 2007 JavaOne SM Conference Session TS

35 AspectJ (2) AspectJ requires a special compiler can be used with the standard compiler does its work when classes are loaded at runtime most syntax errors are only detected at runtime 2007 JavaOne SM Conference Session TS

36 Using AOP to Add Probes to public class MyAspect { static TempFileStats tempfilestats = new java.io.file.createtempfile(..))") public void updatetempfilestats() { tempfilestats.addcall(); } } 2007 JavaOne SM Conference Session TS

37 Using AOP to Add Probes to Code public void saveconfig() { String config =...; tempfilestats.addcall(); } File tmp = File.createTempFile( config, null); OutputStream out = new FileOutputStream(tmp);... This can happen When the code is compiled When the compiled classes are loaded 2007 JavaOne SM Conference Session TS

38 Agenda Introduction to JMX Technology Some Uses of the Technology Aspect-Oriented Programming Java Specification Requests (JSRs) JSR 255 (JMX API 2.0) JSR 262 (Web Services Connector) 2007 JavaOne SM Conference Session TS

39 WORK IN PROGRESS 2007 JavaOne SM Conference Session TS

40 Some New Features in JMX API 2.0 Scheduled for Java SE platform, version 7 Hierarchical namespace Cascading Event service Support for locales Annotations to define MBeans Custom-type mapping for MXBeans 2007 JavaOne SM Conference Session TS

41 Cascading (Federation) Master MBean Server server1// server2// server1//com.sun:type=whatever Remote Server 1 Remote Server 2 com.sun:type=whatever 2007 JavaOne SM Conference Session TS

42 Cascading Uses a special NamespaceHandler that forwards everything to a remote MBean Server Clients can connect to the Master MBean Server and access MBeans in remote servers Don t need to know how to connect to those servers Those servers might be on an inaccessible subnet Clients can subscribe to notifications from the remote MBeans in the same way 2007 JavaOne SM Conference Session TS

43 Namespaces MBean Server foo// bar// com.baz:type=cachecontrol foo//com.sun:type=whatever 2007 JavaOne SM Conference Session TS

44 Namespaces Namespaces are like filesystem directories ObjectNames beginning with foo// are in the foo// namespace foo//com.sun:type=whatever Each namespace has a NamespaceHandler Handler for foo// handles all MBeans whose name begins with foo// NamespaceHandler is itself an MBean 2007 JavaOne SM Conference Session TS

45 Support for Locales Default Locale Client getmbeaninfo(cache) Cache configuration & statistics getattribute(cache, LastError ) Cache overflow MBean Server French Locale Client getmbeaninfo(cache) Configuration & statistiques du cache getattribute(cache, LastError ) Débordement du cache MBean Server 2007 JavaOne SM Conference Session TS

46 Support for Locales Clients can add a locale to an MBean Server connection French-locale client sees the connection through French-tinted glasses Descriptions in MBeanInfo are replaced by French equivalents if available MBean can see it is being accessed in the French locale and return localized messages 2007 JavaOne SM Conference Session TS

47 Annotations to Define MBeans Number one feature request from our users Already exists in some environments, e.g., public class CacheControl implements CacheControlMBean public int getsize() public void setsize(int size) public int getused() {...} public int dropoldest(int n) {...} 2007 JavaOne SM Conference Session TS

48 Agenda Introduction to JMX Technology Some Uses of the Technology Aspect-Oriented Programming Java Specification Requests (JSRs) JSR 255 (JMX API 2.0) JSR 262 (Web Services Connector) 2007 JavaOne SM Conference Session TS

49 Web Services Connector Being defined by JSR 262. Early Draft 2. Java platform clients can use JMX Remote API Allows clients of JMX agents on non-java platforms Can exploit web infrastructure Client SOAP Message Request Server MBean Server Response 2007 JavaOne SM Conference Session TS

50 JMX Compliant Connector Transparent usage for JMX technology clients Just a matter of URL service:jmx:rmi://... X service:jmx:ws://<host>:<port>/<http context> But pay attention to types 2007 JavaOne SM Conference Session TS

51 Java Types XML Serialization Built in supported types Java platform basic and primitive types (integer, long, date ) Map, list JMX API types (CompositeData, TabularData, OpenType, ObjectName, Relation, Role, ) Arrays of above types Extensible with your custom types (Java Architecture for XML Binding [JAXB]) Use MXBeans! 2007 JavaOne SM Conference Session TS

52 Connector Usage Client-side JMXServiceURL url = new JMXServiceURL( service:jmx:ws://server1:80/jmxws ); JMXConnector connector = JMXConnectorFactory.newJMXConnector(url, null); MBeanServerConnection connection = connector.getmbeanserverconnection(); connection.getattribute(...); Server-side JMXServiceURL url = new JMXServiceURL( service:jmx:ws://server1:80/jmxws ); server = JMXConnectorServerFactory.newJMXConnectorServer(url, null, ManagementFactory.getPlatformMBeanServer()); server.start(); 2007 JavaOne SM Conference Session TS

53 WS-Management Previous early draft based on custom protocol Early draft two based on DMTF WS-Management (WS-Man) protocol General SOAP-based protocol (SOAP 1.2) For managing systems (servers, devices ) Allows for interaction with manageable resources Physical such as a device, a printer Logical such as an application, a service Relies on existing set of WS-* specifications 2007 JavaOne SM Conference Session TS

54 WS-Management General SOAP-based protocol (SOAP 1.2) For managing systems (servers, devices, applications, services ) Allows for interaction with manageable resources Physical such as a device, a printer Logical such as an application, a service Relies on existing set of web service specifications (WS-*) 2007 JavaOne SM Conference Session TS

55 WS-* Standards WS-Addressing Resource referencing (endpoint reference) WS-Transfer Resource creation/deletion Read/write resource properties Invoke resource operations WS-Enumeration Resource enumeration (references and values) WS-Eventing Receive resource notifications 2007 JavaOne SM Conference Session TS

56 WS-A SOAP Message Headers <env:envelope> <env:header> <wsa:to> <wsa:replyto> <wsa:address> us </wsa:address> </wsa:replyto> <wsa:action> <wsa:messageid>uuid:e384bd86-b a-8fcb157ae6d813f4</wsa:messageid> <wsman:resourceuri>printer</wsman:resourceuri> <wsman:selectorset> <wsman:selector Name="ID">xm3</wsman:Selector> </wsman:selectorset> </env:header> <env:body/> </env:envelope> 2007 JavaOne SM Conference Session TS

57 WS-Man SOAP Message Headers <env:envelope> <env:header> <wsa:to> <wsa:replyto> <wsa:address> us </wsa:address> </wsa:replyto> <wsa:action> <wsa:messageid>uuid:e384bd86-b a-8fcb157ae6d813f4</wsa:messageid> <wsman:resourceuri>printer</wsman:resourceuri> <wsman:selectorset> <wsman:selector Name="ID">xm3</wsman:Selector> </wsman:selectorset> </env:header> <env:body/> </env:envelope> 2007 JavaOne SM Conference Session TS

58 WS-Transfer Get Response <env:envelope> <env:header> <wsa:to> <wsa:action> <wsa:messageid>uuid:3cbfc230-0f27-4cf6-a0c </wsa:messageid> <wsa:relatesto>uuid:e384bd86-b a-8fcb157ae6d813f4</wsa:relatesto> </env:header> <env:body> <Printer model= Laser A3 > <Paper>Empty</Paper> <Ink>50%</Ink> </Printer> </env:body> </env:envelope> 2007 JavaOne SM Conference Session TS

59 WS-Man Resource Identified by a WS-A endpoint reference Associated with an XML schema (XSD) Has a type: <wsman:resourceuri> Multiple instances of the same type: <wsman:selector> Has values Has operations Can emit notifications 2007 JavaOne SM Conference Session TS

60 JMX Technology MBean Identified by an ObjectName Associated with an MBeanInfo Multiple instances of the same type: ObjectName keys Has values: MBean Attributes Has operations: MBean Operations Can emit notifications: MBean Notifications 2007 JavaOne SM Conference Session TS

61 WS-Man Resource == MBean? Yes, they are very similar concepts but JavaOne SM Conference Session TS

62 MBean to Resource Mapping (1/2) No way to strictly map an MBean type to a WS-Man resourceuri Composing a specific XSD from an MBeanInfo not trivial What about namespace? Which mapping to follow (WS-CIM, JAXB software, custom one)? Do we really want specific XSD? 2007 JavaOne SM Conference Session TS

63 MBean to WS-Man Resource Mapping A schema per MBean Interface? JMX technology offers a generic access to MBeans getattribute( MyAttribute ) invoke( myoperation,...) setattribute( MyAttribute,...) All MBeans share the same representation, the MBeanInfo All MBeans could share the same schema in the WS-Man world 2007 JavaOne SM Conference Session TS

64 MBean WS-Man Resource MBeans are mapped to a single generic WS-Man resource type MBean is exposed as a DynamicMBeanResource Representation very similar to Dynamic MBean WS-Man resource XML element represents MBean Attributes and MBeanInfo Single invoke operation 2007 JavaOne SM Conference Session TS

65 MBean WS-Man Resource Schema <xs:element name="dynamicmbeanresource"> <xs:complextype> <xs:sequence> <!-- The list of Resource properties --> <xs:element ref="property" minoccurs="0" maxoccurs="unbounded"/> <!-- The Resource Metadata (XML representation of JMX MBeanInfo --> <xs:element ref="jmx:resourcemetadata"/> </xs:sequence> </xs:complextype> </xs:element> 2007 JavaOne SM Conference Session TS

66 MBean WS-Man Resource Schema <xs:element name="dynamicmbeanresource"> <xs:complextype> <xs:sequence> <!-- The list of Resource properties --> <xs:element ref="property" minoccurs="0" maxoccurs="unbounded"/> <!-- The Resource Metadata (XML representation of JMX MBeanInfo --> <xs:element ref="jmx:resourcemetadata"/> </xs:sequence> </xs:complextype> </xs:element> 2007 JavaOne SM Conference Session TS

67 MBean WS-Man Resource Schema <xs:element name="dynamicmbeanresource"> <xs:complextype> <xs:sequence> <!-- The list of Resource properties --> <xs:element ref="property" minoccurs="0" maxoccurs="unbounded"/> <!-- The Resource Metadata (XML representation of JMX MBeanInfo --> <xs:element ref="jmx:resourcemetadata"/> </xs:sequence> </xs:complextype> </xs:element> 2007 JavaOne SM Conference Session TS

68 WS-Man View of a getattribute Boolean b = (Boolean) connection.getattribute(new ObjectName( java.lang:type=memory ), Verbose ); <env:envelope> <env:header> <wsa:action> </wsa:action> <wsman:selectorset> <wsman:selector Name="ObjectName"> java.lang:type=memory </wsman:selector> </wsman:selectorset> <wsman:resourceuri> </wsman:resourceuri> <wsman:fragmenttransfer> //jmx:property[@name="verbose"] </wsman:fragmenttransfer> 2007 JavaOne SM Conference Session TS

69 WS-Man View of a getattribute Boolean b = (Boolean) connection.getattribute(new ObjectName( java.lang:type=memory ), Verbose ); <env:envelope> <env:header> <wsa:action> </wsa:action> <wsman:selectorset> <wsman:selector Name="ObjectName"> java.lang:type=memory </wsman:selector> </wsman:selectorset> <wsman:resourceuri> </wsman:resourceuri> <wsman:fragmenttransfer> //jmx:property[@name="verbose"] </wsman:fragmenttransfer> 2007 JavaOne SM Conference Session TS

70 WS-Man View of a getattribute Boolean b = (Boolean) connection.getattribute(new ObjectName( java.lang:type=memory ), Verbose ); <env:envelope> <env:header> <wsa:action> </wsa:action> <wsman:selectorset> <wsman:selector Name="ObjectName"> java.lang:type=memory </wsman:selector> </wsman:selectorset> <wsman:resourceuri> </wsman:resourceuri> <wsman:fragmenttransfer> //jmx:property[@name="verbose"] </wsman:fragmenttransfer> 2007 JavaOne SM Conference Session TS

71 WS-Man View of a getattribute Boolean b = (Boolean) connection.getattribute(new ObjectName( java.lang:type=memory ), Verbose ); <env:envelope> <env:header> <wsa:action> </wsa:action> <wsman:selectorset> <wsman:selector Name="ObjectName"> java.lang:type=memory </wsman:selector> </wsman:selectorset> <wsman:resourceuri> </wsman:resourceuri> <wsman:fragmenttransfer> //jmx:property[@name="verbose"] </wsman:fragmenttransfer> 2007 JavaOne SM Conference Session TS

72 WS-Man View of a getattribute <env:envelope>... <env:body> <wsman:xmlfragment> <jmx:property name="verbose"> <jmx:boolean>false</jmx:boolean> </jmx:property> </wsman:xmlfragment> </env:body> <env:envelope> 2007 JavaOne SM Conference Session TS

73 Mapping Is Not Only for MBeans JMX technology notification fetching Extended WS-Eventing Pull mode to handle multiple subscription querynames/querymbeans WS-Enumeration of MBean resources getdomains/getdefaultdomain MBeanServer WS-Man resource JSR 262 specification provides a complete MBeanServer operation to WS-Man mapping 2007 JavaOne SM Conference Session TS

74 Web Services Connector Security Authentication: HTTP basic authentication Privacy: HTTPS (SSL) Authorization: JMX technology permissions 2007 JavaOne SM Conference Session TS

75 Web Services Connector RI Early Access 2: Runs on Java platform 5 and Java SE platform 6 Java APIs for XML Web Services (JAX-WS) endpoint WiseMan java.net project Open source WS-Man Java implementation 1.0 RC release Supported types extensible thanks to JAXB 2007 JavaOne SM Conference Session TS

76 JSR 262 Interop Demos 1.HP OVO Management Console to monitor JMX MBeans (Rachal Denis, HP) 2.Microsoft Vista Windows Remote Management to Manage and Monitor JMX MBeans 3.Microsoft Vista Event Viewer to Monitor JMX MBeans 2007 JavaOne SM Conference Session TS

77 DEMO Interoperation Using WS-Management 2007 JavaOne SM Conference Session TS

78 Demos Architecture Windows Vista JSR 262 Solaris, Linux, Windows JavaOne SM Conference Session TS

79 Demos Architecture, HP OVO HP OVO Console Windows 2003 Server WS-Man Protocol OVO API HP OVO Agent Windows Vista JSR 262 Solaris, Linux, Windows JavaOne SM Conference Session TS

80 Demos Architecture, WinRM VBScript HP OVO Console HP OVO Agent Windows 2003 Server Windows Vista WinRM VBScript WS-Man Protocol OVO API RMI JSR 262 Solaris, Linux, Windows... JConsole 2007 JavaOne SM Conference Session TS

81 Demos Architecture, Event Viewer HP OVO Console HP OVO Agent Windows 2003 Server Windows Vista WinRM VBScript WS-Man protocol OVO API RMI Event Viewer JSR 262 Solaris, Linux, Windows... JConsole 2007 JavaOne SM Conference Session TS

82 Demos Architecture HP OVO Console HP OVO Agent Windows 2003 Server Windows Vista WinRM VBScript WS-Man Protocol OVO API RMI Event Viewer JSR 262 Solaris, Linux, Windows... JConsole 2007 JavaOne SM Conference Session TS

83 HP OVO/JSR 262 Demos Clients HP OVO Management Console Monitoring of Old Gen Memory Pool Thanks to WS-Man VBScripting JMX technology with WS-Man VBScript examples to manage JMX technology MBeans Server-side Java SE platform 6 Java Virtual Machine (JVM ) JConsole to set thresholds JVM software MXBean Memory MXBean Runtime MXBean The terms Java Virtual Machine and JVM mean a Virtual Machine for the Java platform JavaOne SM Conference Session TS

84 JSR 262 Resources JSR 262 RI JMX homepage WiseMan project JavaOne SM Conference Session TS

85 Summary Lots of stuff happening in the JMX technology world JMX API 2.0 will add some exciting new stuff JSR 262 will increase interoperability with the world outside the Java platform 2007 JavaOne SM Conference Session TS

86 For More Information LAB-1420: Monitoring and Troubleshooting using JMX Technology and JConsole TS-1106: Creating Manageable Systems With JMX, Spring AOP, and Groovy (today at 5:30 pm) BOF-1613: Using JMX Technology for Monitoring Widely Distributed Networks (today at 7:55 pm) Pavilion booth 965 (today at 1:00 3:00 pm) JavaOne SM Conference Session TS

87 Q&A 2007 JavaOne SM Conference Session TS

88 Java Management Extensions (JMX ) Technology: Who s Doing What Éamonn McManus JMX Specification Lead Sun Microsystems x Session TS-2656 Jean-François Denise JMX Technology Team Sun Microsystems JavaOne SM Conference Session TS-2656