Comments on: JMX Scripts using JRuby http://jmesnil.net/weblog/2007/03/23/jmx-scripts-using-jruby/ Thoughts about Java, Web and Software Development Sat, 19 Jul 2008 06:42:47 +0000 http://wordpress.org/?v=2.5 By: GSIY … Ruby-Rails Portal http://jmesnil.net/weblog/2007/03/23/jmx-scripts-using-jruby/#comment-51089 GSIY … Ruby-Rails Portal Wed, 05 Sep 2007 16:02:30 +0000 http://jmesnil.net/weblog/2007/03/13/jmx-scripts-using-jruby/#comment-51089 [...] of JMX on JRuby came up recently and I decided to play around. I found a great starter on Jeff Mesnil’s blog, but I decided I hated the syntax. Ruby has spoiled me. Ac [...] […] of JMX on JRuby came up recently and I decided to play around. I found a great starter on Jeff Mesnil’s blog, but I decided I hated the syntax. Ruby has spoiled me. Ac […]

]]> By: Jeff Mesnil’s Weblog » Blog Archive » JMX Scripts using JRuby http://jmesnil.net/weblog/2007/03/23/jmx-scripts-using-jruby/#comment-42929 Jeff Mesnil’s Weblog » Blog Archive » JMX Scripts using JRuby Mon, 16 Jul 2007 09:45:56 +0000 http://jmesnil.net/weblog/2007/03/13/jmx-scripts-using-jruby/#comment-42929 [...] :newPlatformMXBeanProxy instead of MBeanServerInvocationHandler::newProxyInstance based on Daniel comment] I needed to write a script to automate the managemen [...] […] :newPlatformMXBeanProxy instead of MBeanServerInvocationHandler::newProxyInstance based on Daniel comment] I needed to write a script to automate the managemen […]

]]> By: Jeff Mesnil’s Weblog » Blog Archive » JMX Scripts using JRuby — Part II http://jmesnil.net/weblog/2007/03/23/jmx-scripts-using-jruby/#comment-34397 Jeff Mesnil’s Weblog » Blog Archive » JMX Scripts using JRuby — Part II Thu, 31 May 2007 09:57:25 +0000 http://jmesnil.net/weblog/2007/03/13/jmx-scripts-using-jruby/#comment-34397 [...] e_method instead of eval based on a poignant explanation of eval-less metaprogramming. In Part I, I created a JRuby script to manage a Java application using JMX. In this e [...] […] e_method instead of eval based on a poignant explanation of eval-less metaprogramming. In Part I, I created a JRuby script to manage a Java application using JMX. In this e […]

]]> By: Daniel Fuchs http://jmesnil.net/weblog/2007/03/23/jmx-scripts-using-jruby/#comment-20200 Daniel Fuchs Thu, 22 Mar 2007 19:26:41 +0000 http://jmesnil.net/weblog/2007/03/13/jmx-scripts-using-jruby/#comment-20200 Hi Jeff, Nice blog entry, but I'd like to bring something to your attention: The MBeans used in the JVM Management & Monitoring API are not regular MBeans, they're MXBeans. Although generic support for custom MXBeans was only added in JDK 6, JDK 5 had a built-in support for M&M MXBeans. In the general case, using MBeanServerInvocationHandler.newProxyInstance __does not work__ for MXBean interfaces. Instead you should be using ManagementFactory.newPlatformMXBeanProxy as I have explained in one of my posts: [http://blogs.sun.com/jmxetc/entry/how_to_retrieve_remote_jvm#comment-1174563727000](http://blogs.sun.com/jmxetc/entry/how_to_retrieve_remote_jvm#comment-1174563727000) MBeanServerInvocationHandler.newProxyInstance works only for regular MBeans. In other words: * JDK 6 JMX.newMBeanProxy is equivalent to JDK 5 MBeanServerInvocationHandler.newProxyInstance * JDK 6 JMX.newMXBeanProxy is a more general method for JDK 5 ManagementFactory.newPlatformMXBeanProxy (newMXBeanProxy works for any MXBeans, newPlatformMXBeanProxy will/might only work for platform MXBeans). So you should correct your code and use ManagementFactory.newPlatformMXBeanProxy instead of MBeanServerInvocationHandler.newProxyInstance. Hope this helps, -- daniel Hi Jeff,

Nice blog entry, but I’d like to bring something to your attention:

The MBeans used in the JVM Management & Monitoring API are not
regular MBeans, they’re MXBeans.
Although generic support for custom MXBeans was only added in JDK 6,
JDK 5 had a built-in support for M&M MXBeans.

In the general case, using MBeanServerInvocationHandler.newProxyInstance
does not work for MXBean interfaces. Instead you should be
using ManagementFactory.newPlatformMXBeanProxy as I have explained
in one of my posts:
http://blogs.sun.com/jmxetc/entry/howtoretrieveremotejvm#comment-1174563727000

MBeanServerInvocationHandler.newProxyInstance works only for regular
MBeans.

In other words:

  • JDK 6 JMX.newMBeanProxy is equivalent to JDK 5
    MBeanServerInvocationHandler.newProxyInstance
  • JDK 6 JMX.newMXBeanProxy is a more general method for JDK 5
    ManagementFactory.newPlatformMXBeanProxy (newMXBeanProxy works
    for any MXBeans, newPlatformMXBeanProxy will/might only work for
    platform MXBeans).

So you should correct your code and use
ManagementFactory.newPlatformMXBeanProxy instead of
MBeanServerInvocationHandler.newProxyInstance.

Hope this helps,

– daniel

]]>