JDK-6898160 : Need serviceability support for new vm argument type 'uint64_t'
  • Type: Bug
  • Component: hotspot
  • Sub-Component: runtime
  • Affected Version: hs17
  • Priority: P2
  • Status: Closed
  • Resolution: Fixed
  • OS: generic
  • CPU: generic
  • Submitted: 2009-11-04
  • Updated: 2011-03-07
  • Resolved: 2011-03-07
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 6 JDK 7 Other
6u18Fixed 7Fixed hs16Fixed
Related Reports
Relates :  
Relates :  
Description
A new vm argument type, 'uint64_t', was added as part of 6887571.  The jdk library
code in jdk/share/native/sun/management/Flag.c that fetches all the vm product flags
throws an exception if it doesn't understand the type of an argument.  The change
for 6887571 didn't include full serviceability support for uint64_t.
This bug affects the following SDK/JDK test in the MM_REGRESSION
test suite:

    com/sun/management/HotSpotDiagnosticMXBean/GetDiagnosticOptions.java

Comments
EVALUATION http://hg.openjdk.java.net/hsx/hsx16/master/rev/26d0c7276c9e
13-11-2009

EVALUATION http://hg.openjdk.java.net/hsx/hsx16/baseline/rev/26d0c7276c9e
07-11-2009

EVALUATION http://hg.openjdk.java.net/jdk7/hotspot-rt/hotspot/rev/ba7ea42fc66e
05-11-2009

SUGGESTED FIX If a flag has a type unknown to the jdk library, then assert in debug builds and ignore it in product builds.
04-11-2009

SUGGESTED FIX Add serviceability support for uint64_t.
04-11-2009

EVALUATION A new vm argument type, 'uint64_t', was added as part of the fix for 6887571, but full serviceability support wasn't done in the vm. The jdk library code in jdk/src/share/native/sun/management/Flag.c throws an exception if it doesn't understand the type of a vm argument, hence the problem. *** (#1 of 1): [ UNSAVED ] ###@###.###
04-11-2009