lang-management modification - it may break customer application?
mandy.chung at oracle.com
Thu Jun 30 05:06:49 UTC 2011
I'm including the serviceability-dev mailing list as
java.lang.management is a serviceability feature.
On 6/30/11 12:32 PM, Jing LV wrote:
> I see there is some modifiction in the
> java.lang.management.ManagementFactory, e.g, newPlatformMXBeanProxy. The
> LogManager.LOGGING_MXBEAN_NAME in Java7 has been changed and now
> represents PlatformLoggingMXBean rather than
If it's accessed via an MBeanServer, this should not make any difference
since both LoggingMXBean and PlatformLoggingMXBean defines the same
> I understand this is the stradegy to move all MXBean into
> java.lang.management package. However in JDK6, customers may already use
> java.lang.management.ManagementFactory.newPlatformMXBeanProxy(someserver, LogManager.LOGGING_MXBEAN_NAME,
> LoggingMXBean) to get LoggingMXBean and in JDK7 he would meet a
This should work in both JDK 6 and JDK 7. A regression test in the JDK
checks this method retains the same behavior:
LoggingMXBean proxy =
Do you have a test case reproducing IAE?
More information about the core-libs-dev