Vladimir, I believe you don’t want to add the dependency from JVMCI to java.management. Otherwise, JVMCI can’t run with only java.base. Is the MBean in jdk.internal.vm.compiler or in Lab’s Graal compiler?
src/jdk.internal.vm.ci/share/classes/jdk/vm/ci/services/src/jdk/vm/ci/services/internal/JVMCIMXBeans.java - I suspect this file meant to be in src/jdk.internal.vm.ci/share/classes/src/jdk.internal.vm.ci/share/classes/jdk/vm/ci/services/internal/JVMCIMXBeans.java Mandy > On Jul 12, 2017, at 2:20 PM, Vladimir Kozlov <vladimir.koz...@oracle.com> > wrote: > > https://bugs.openjdk.java.net/browse/JDK-8182701 > webrev: > http://cr.openjdk.java.net/~kvn/8182701/webrev.jdk/ > http://cr.openjdk.java.net/~kvn/8182701/webrev.hs/ > > Contributed by Jaroslav Tulach. > > JDK itself contains quite a lot of platform MBeans which get registered "on > demand". Graal compiler (jdk.internal.vm.compiler) provides its own MBean(s) > - however currently there is no way to register it "on demand". JDK9 already > contains support for collecting platform MBeans from various modules. We just > need to expose Graal MBean through JVMCI. > > Thanks, > Vladimir
