I just thought I'd respond to Jean-Francois's excellent blog articles on accessing JMX instrumentation through web-services and more especially, using JSR 262 Web Service Connector for JMX to accesss JMX instrumentation.
This shows how simple it is to access the xVM's upcoming public management APIs using a Windows client using winrm, Microsoft's ws-management client. It can connect to the xVM management stack using ws-management via a secured https connection with http basic authentication.
[Read More]( Nov 07 2008, 06:19:04 PM CET ) Permalink
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...
Here's a new feature in Java 7 that can help you to create self-signed certificates that are immune to this...
( Nov 19 2007, 03:20:28 PM CET ) Permalink
( Jun 22 2007, 03:37:26 PM CEST ) Permalink
( May 29 2007, 04:11:10 PM CEST ) Permalink
( May 22 2007, 11:54:27 AM CEST ) Permalink
System.out and System.err
to your Java Logging subsystem, so that such output gets integrated into
your debug log stream in a rolling log file.( Jan 18 2007, 02:13:47 PM CET ) Permalink Comments [7]
( Jan 16 2007, 06:00:00 PM CET ) Permalink Comments [4]
However, it's necessary for clients to individually subscribe to each MBean that they are interested in receiving notifications from. When there are many such MBeans, or when the MBeans may be created dynamically, this can pose a problem for the client.
This article shows how to build a JMX Notification Hub MBean which provides a single place for clients to subscribe to receive notifications from many MBeans. [Read More]
( Nov 10 2006, 04:41:35 PM CET ) Permalink
( Oct 31 2006, 11:44:33 AM CET ) Permalink
( Oct 23 2006, 05:00:00 PM CEST ) Permalink
I'm more of a J2SE and JMX domain expert myself, the work we do is often used in management service tiers and management agent tiers, and it does me some good to make sure I track other technologies. I've signed up and will be following some but not all of the coursework...
( Oct 09 2006, 03:00:00 PM CEST ) Permalink
Have you ever wondered why an otherwise idle Java process sits there
in an endless loop scheduling a thread, calling poll,
regularly eating a small amount of CPU?
I always used to think that this was because of things like the garbage-collector and the JIT compiler, but it's not...
[Read More]( Sep 29 2006, 03:00:00 PM CEST ) Permalink
In my last blog entry, I described how it's possible to get synchronized access to multiple attributes of the same MBean via the use of a SnapshotProxy and a SynchronizedStandardMBean.
This blog entry describes the SnapshotProxy in more detail.
( Sep 11 2006, 04:00:00 PM CEST ) Permalink Comments [2]
I was recently reading an excellent article by JMX Spec Lead Éamonn McManus called MXBeans in Java SE 6: Bundling Values Without Special JMX Client Configurations, which describes a great Java 6 platform feature related to management - that of supporting MXBeans - gone are your classpath issues with proprietory serialized Objects being sent over a JMX connection.
Although MXBeans are a very suitable general-purpose approach to this question, and MXBeans are what I'd recommend if you're able to use Java 6 and are able to choose your own data model, they're not the only way of getting access to MBean attributes in an atomic manner. This entry explains another approach to a slightly different problem-space - that of accessing different attributes in an atomic manner, rather than grouping the attributes together into a single, composite attribute.
[Read More]( Sep 08 2006, 05:30:00 PM CEST ) Permalink