Small issues with JMH + JOL on JDK-9
Aleksey Shipilev
aleksey.shipilev at oracle.com
Thu Mar 31 11:48:56 UTC 2016
On 03/31/2016 12:16 PM, Attila-Mihaly Balazs wrote:
> JMH fails on JDK 9-ea, VM 9-ea+110 with the exception:
>
> Exception in thread "main" java.util.ServiceConfigurationError:
> sun.management.spi.PlatformMBeanProvider: Provider
> jdk.management.cmm.internal.PlatformMBeanProviderImpl not found
> at java.util.ServiceLoader.fail(ServiceLoader.java:237)
> at java.util.ServiceLoader.access$300(ServiceLoader.java:183)
> at
Yes, this is a known bug in b110. Forget that build :)
https://bugs.openjdk.java.net/browse/JDK-8152161
> (However it works as expected with JDK 9-ea, VM 9-ea+111 - so this is just
> a heads up / FYI that there might be the need of an additional unit /
> integration test in OpenJDK).
FYI also, b111 introduces some new issues for JMH, hopefully resolved
with the upcoming JMH release.
> Also, since ea+111 JOL logs the following thing:
JOL requires much more work than that. Luckily, current failure does not
preclude JOL from working, it just less accurate.
-Aleksey
More information about the jmh-dev
mailing list