Luis-Miguel Alventosa's Blog

Wednesday June 28, 2006

Changes to the MBeans tab look and feel in Mustang JConsole

Moving the nested tabs for Attributes/Operations/Notifications/Info from the MBean's right panel to the MBean tree in the left panel has implied modifications to the MBeans tab look and feel.

Let's introduce the new Mustang JConsole features by comparison with the Tiger JConsole MBeans tab look and feel.

Friday June 23, 2006

Using the SSL/TLS-based RMI Socket Factories in Java SE 6 with the JNDI/RMI Registry Service Provider

This is a followup of my previous blog entry Using the SSL/TLS-based RMI Socket Factories in J2SE 5.0.

In this new entry I will update the example to show you how SSL/TLS-based connections to the RMI registry are now supported in Mustang (Java SE 6) when using the JNDI/RMI Registry Service Provider.

Wednesday June 14, 2006

JConsole's MBeans tab: MBean tree construction

Do you want to know how the MBean tree is constructed in the JConsole's MBeans tab in Mustang (Java SE 6)?

If the answer is yes, keep reading!

I will explain how the MBean tree is constructed by default and how you can specify the key order the MBean tree construction algorithm must follow when adding MBeans (ObjectNames) to the MBean tree.

Friday June 02, 2006

Mimicking the out-of-the-box JMX management agent in J2SE 5.0

Starting with J2SE 5.0, the JVM is instrumented for monitoring and management providing built-in ("out-of-the-box") management capabilities for both remote and local access. The JVM includes a platform MBean server and platform MBeans that JMX management applications can use. You can also instrument and monitor your own applications by adding your application specific MBeans to the platform MBean server.

By default, remote access to the out-of-the-box management agent is protected by authentication (password files), authorization (access files) and SSL/TLS encryption. All the out-of-the-box management agent configuration is performed through system properties and/or through a management.properties file (located under JRE_HOME/lib/management/management.properties). For more detailed info about the Monitoring and Management APIs in the Java platform have a look at the Monitoring and Management Guide.

In most of the cases using the out-of-the-box management agent and configuring it through the management.properties file is enough but there are some cases such as when exporting the RMI server remote objects in a given port to allow firewall traversing, or exporting the RMI server remote objects using a specific network interface in multi-homed systems, etc, where it may not be enough. For such cases we can mimic the behavior of the out-of-the-box management agent by directly using the JMX Remote API to programmatically create, configure and deploy the management agent.