JDK-6581408 : Most of serviceability tools fail in 6u3b01 due to version check
  • Type: Bug
  • Component: core-svc
  • Sub-Component: tools
  • Affected Version: 6u3,7
  • Priority: P2
  • Status: Resolved
  • Resolution: Fixed
  • OS: generic,linux_sun
  • CPU: generic
  • Submitted: 2007-07-17
  • Updated: 2012-02-02
  • Resolved: 2007-09-12
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
6u4 b03Fixed 7Fixed
Related Reports
Duplicate :  
JDK-6582065 - sun/tools/jinfo/Basic.sh test is failing against 6u03
Duplicate :  
JDK-6475822 - SA:Fix vm version check for 1.7
Relates :  
JDK-6590301 - HotSpot VM should have own version separate from JDK version
Description
Most serviceability tools from 6u3 b01 (except jstack) cannot be used on 6u3 b01 process:

$ /set/vmsqe/jdk-builds/6/latest/solaris-amd64/bin/jmap 29386
Attaching to process ID 29386, please wait...
Exception in thread "main" java.lang.reflect.InvocationTargetException
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
        at java.lang.reflect.Method.invoke(Method.java:597)
        at sun.tools.jmap.JMap.runTool(JMap.java:178)
        at sun.tools.jmap.JMap.main(JMap.java:110)
Caused by: sun.jvm.hotspot.runtime.VMVersionMismatchException: Supported versions are 1.7.0. Target VM is 1.6.0_03-ea-b01
        at sun.jvm.hotspot.runtime.VM.checkVMVersion(VM.java:222)
        at sun.jvm.hotspot.runtime.VM.<init>(VM.java:275)
        at sun.jvm.hotspot.runtime.VM.initialize(VM.java:328)
        at sun.jvm.hotspot.bugspot.BugSpotAgent.setupVM(BugSpotAgent.java:594)
        at sun.jvm.hotspot.bugspot.BugSpotAgent.go(BugSpotAgent.java:494)
        at sun.jvm.hotspot.bugspot.BugSpotAgent.attach(BugSpotAgent.java:332)
        at sun.jvm.hotspot.tools.Tool.start(Tool.java:163)
        at sun.jvm.hotspot.tools.HeapSummary.main(HeapSummary.java:39)
        ... 6 more
This also affects "jstack -F" (in this case SA is used)
Comments
EVALUATION In 7.0 hotspot_version file was created to manage the release version number (ex 1.7.0). This version file is used to create a version string for hotspot vm (for non controlled build) and SA. When 7.0 hotspot vm moved to 6u3 this file was not modified. And SA version check depends on this file. Since this file was not changed when it is moved to 6u3 SA version check broke. So SA should be fixed to use the controlled build version string instead of version from this file. -Swamy
24-07-2007