JDK-8175326 : JMap timeout after java.lang.reflect.InaccessibleObjectException
  • Type: Bug
  • Component: hotspot
  • Sub-Component: runtime
  • Affected Version: 10
  • Priority: P3
  • Status: Resolved
  • Resolution: Fixed
  • Submitted: 2017-02-21
  • Updated: 2017-02-27
  • Resolved: 2017-02-27
The Version table provides details related to the release that this issue/RFE will be addressed.

Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.

To download the current JDK release, click here.
JDK 10
10Fixed
Related Reports
Duplicate :  
JDK-8175334 - serviceability/sa/jmap-hprof/JMapHProfLargeHeapTest.java failed on JDK 10
Relates :  
JDK-8152206 - Simplify jvmstat modules
Description
Test: serviceability/sa/jmap-hprof/JMapHProfLargeHeapTest.java

Got this on all platforms in the nightlies:

Exception in thread "main" java.lang.reflect.InaccessibleObjectException: Unable to make field private final sun.management.VMManagement sun.management.RuntimeImpl.jvm accessible: module java.management does not "opens sun.management" to unnamed module @23faf8f2
	at java.base/java.lang.reflect.AccessibleObject.checkCanSetAccessible(AccessibleObject.java:207)
	at java.base/java.lang.reflect.Field.checkCanSetAccessible(Field.java:171)
	at java.base/java.lang.reflect.Field.setAccessible(Field.java:165)
	at JMapHProfLargeHeapProc.getProcessId(JMapHProfLargeHeapProc.java:59)
	at JMapHProfLargeHeapProc.main(JMapHProfLargeHeapProc.java:41)
Comments
[~dholmes] is correct, 8152206 is missing from jdk10. Waiting for the fix to propagate from JDK 9.
22-02-2017
Removed "integration_blocker" as not relevant for 10.
22-02-2017
I think we may just be missing 8152206: Simplify jvmstat modules
22-02-2017
Removing "9" from Affects Version since the above failure is on 10 (nightly was inadvertently run on 10 instead of 9). The failure is real however. I am seeing it with my own testing of 10.
21-02-2017