Dustin Marx has written a rather good post on JMX MXBeans: "I'll demonstrate the tremendous utility of the JMX MXBean in this blog entry. While doing so, I'll also demonstrate the usefulness of a J2SE 5 enum for reporting a set of discrete status values and will demonstrate the highly useful JMX (introduced with Java SE 6) class's newMBeanProxy and newMXBeanProxy methods."

Another excellent article by Dustin Marx: "A Second Look at JMX Web Services Connector: winrm In A First Look at JMX Web Services Connector (also available as a previous blog entry), I demonstrated using JConsole to access a simple sample server using the reference implementation of the JMX Web Services Connector (JSR-262). In this blog entry, I am going to scratch the surface of using Vista's winrm (a WS-Management implementation) to access an MBean server using the JMX Web Services Connector."

My colleague Jean-Francois expands on how to enhance his RESTful adaptor for JMX to handle more complex use cases - like atomic snapshots of dependant data (e.g. a MemoryUsage record) and pulling resource notifications...

"For developers needing another standardized remote JMX connector mechanism free of firewall issues and/or needing to develop JMX clients in a language other than Java, the JMX Web Services Connector should be just the thing they're looking for." [when the JSR 262 is finalized]...

Anyone interested in application manageability and/or management integration should read about Jean-Francois Denise’s prototype for RESTful Access to JMX Instrumentation. Not (at least for now) as something to make use of, but to force us to think pragmatically about the pros and cons of the WS-* stack when used for management integration.

"This is the fourth installment in my summary of the sessions I attended at JavaOne this year. The previous installments covered Java futures, Java programming practice, and concurrency. This one covers JMX stuff."

Jean-Francois Denise presents an in-depth description of the demo performed at the end of the JMX session at JavaOne 2008. In particular, he shows how VBScript was used to interact with a JMX agent through the WS-Management stack provided by the WebServices connector for JMX (JSR 262)

Keddar explains "the communication details between Domain Admin Server, node-agents and server instances in Sun's Application Server 8.x and 9.x (GlassFish V2)." One of these communication channel is JMX.

The author of this post shows "a very simple script [...] to remotely monitor Weblogic JVM Performance and JMS queues using JMX and JRuby." see also http://jmesnil.net/weblog/2008/04/18/monitoring-weblogic-92-with-jmx-and-jruby/

Nice use case of JMX being used to allow dynamic configuration of a SailFin application.

This wiki page explains how to access OpenDS monitoring information through jconsole. And if you can access it from JConsole, you can also access it programatically from Java...

Nice summary of the various troubleshooting tools available in JDK6

Recently I was asked how to do "registerMBean" in a remote JVM, from a remote JMX client. The MBeanServerConnection doesn't expose any registerMBean method, and for good reasons.

My colleague Jean-Francois Denise explains the relationship between the various technologies which are put in play in the WebServices connector for JMX: "This little journey lists the set of standards that have been pressed into service to expose JMX MBeans as WS-Management resources. Luckily we didn't have to implement them all. The JAX-WS (a core Metro component) and WiseMan (a WS-Management Java implementation) projects have been of great help."

Very interesting story about investigating the root cause of an OutOfMemoryError...

JMX is a wonderful tool to monitor and troubleshoot running applications. The new JDK 6 Attach API makes it very easy to attach to a running Java process, and start a JMX agent that will expose monitoring and configuration data to JMX consoles - like JConsole. However, there are some situations where you wish to start a JMX agent on demand, explore the monitoring data or diagnose the probable cause of an observed problem, and then close your JMX agent, leaving the application just how you found it. In this post, I will discuss a means by which you can upload and start such a remotely stoppable JMX agent.

Quote "As the first product from Sun to be released under a GPLv3 license, there's a ton of interest and questions coming up around our Ops Center open source plans." Note: The Common Agent Container is based on JMX and uses Project OpenDMK.

Quote: "Now it is possible to manage Sailfin application like a standard Java EE application, more importantly, start/stop the applications even if they are disabled. The start/stop operations can be performed using any standard jmx console, for ex. jconsole which comes with jdk 6.0 or any JMX compatible Console."

"One of the very useful (and cool) features of compiled JavaFX Script will be closures."

Luis-Miguel: "This is an experimental plugin for VisualVM Preview 2 that allows to add the JConsole tool functionality into the VisualVM tool. This new VisualVM plugin provides support for JConsole core tabs as well as custom JConsole plugins for both local and remote Java applications."

Quote: "After previous post about monitoring JVM memory with MRTG I've got few comments suggesting that it should be possible to do the same thing via SNMP protocol, support for which is built in into JVM at least since version 1.5. It seems like a better approach, at least from system load prospective (no need to run jstat/jps every few minutes) and apparently enabling SNMP agent in the JVM suppose to have very negligible impact on JVM performance. "

Nick explains how to generate self-signed certificate which will work with out-of-sync machines whose clock have a value which predate the time at which the certificate was created: quote: "Have you ever had to deal with clock-skew across machines? When distributing self-signed certificates to create a network of trust between machines, clock-skew can be a real problem if one machine thinks that the other machine's certificate isn't yet valid... your certificate won't be accepted."

VisualVM is a recent (and early) development based on the NetBeans Platform. It strikes an interesting balance between monitoring (a la JConsole), profiling (a la NetBeans Profiler, including a heap walker), and troubleshooting (new in Java 6).

The new MBean Browser plugin is available at the VisualVM Preview 2 Plugins Center and integrates JConsole's MBeans tab functionality into the VisualVM tool.

Quote: "Recently I needed to store some settings in a JSR-181 webservice. Since I did not have a user interface and I don’t want to use property files I thought to try and store them in a MBean using JMX. This gives the administrator the change to alter the properties through the Oracle Enterprise Manager instead of digging for property files on the server."