The following test failed in my baseline JDK7-B131 testing on Solaris X86:

    heapdump/JMapHeap

The configuration being tested is:

    java version "1.7.0-ea"
    Java(TM) SE Runtime Environment (build 1.7.0-ea-b131)
    Java HotSpot(TM) Server VM (build 21.0-b02-fastdebug, mixed mode)

Here is a snippet from the .log file:

[2011-02-26T09:47:55.54] ${TONGA_EXECUTE} ${TEST_ARGS}
[2011-02-26T09:47:55.54] # Actual: /bin/bash /work/shared/test_results/jdk7/base
line/solaris-i586/b131/vm-heapdump-prod-server-fast-mixed.solaris-i586/dcubed.Su
nOS.x86/JMapHeap/run.sh
[2011-02-26T09:47:55.54] Starting eating heap.
[2011-02-26T09:48:11.10] Executing /work/shared/baseline_jdks/1.7.0_b131/solaris
-i586/bin/jmap -dump:format=b,file=heap.bin 29047
[2011-02-26T09:48:11.10] Java HotSpot(TM) Server VM warning: door_call when not
enabled
[2011-02-26T09:48:11.10] VM option 'DefaultMaxRAMFraction=8'
[2011-02-26T09:48:11.10] VM option '-UseGCOverheadLimit'
[2011-02-26T09:48:11.10] Dumping heap to /work/shared/test_results/jdk7/baseline
/solaris-i586/b131/vm-heapdump-prod-server-fast-mixed.solaris-i586/dcubed.SunOS.
x86/JMapHeap/heap.bin ...
[2011-02-26T09:48:11.10] Exception in thread "main" java.io.IOException: Unable
to enqueue command to target VM: Internal error
[2011-02-26T09:48:11.10] at sun.tools.attach.SolarisVirtualMachine.enqueu
e(Native Method)
[2011-02-26T09:48:11.10] at sun.tools.attach.SolarisVirtualMachine.execut
e(SolarisVirtualMachine.java:130)
[2011-02-26T09:48:11.10] at sun.tools.attach.HotSpotVirtualMachine.execut
eCommand(HotSpotVirtualMachine.java:213)
[2011-02-26T09:48:11.10] at sun.tools.attach.HotSpotVirtualMachine.dumpHe
ap(HotSpotVirtualMachine.java:180)
[2011-02-26T09:48:11.10] at sun.tools.jmap.JMap.dump(JMap.java:242)
[2011-02-26T09:48:11.10] at sun.tools.jmap.JMap.main(JMap.java:140)
[2011-02-26T09:48:11.10] Java exited with exit status: 1
[2011-02-26T09:48:11.10] TEST FAILED
[2011-02-26T09:48:11.10] java version "1.7.0-ea"
[2011-02-26T09:48:11.10] Java(TM) SE Runtime Environment (build 1.7.0-ea-b131)
[2011-02-26T09:48:11.10] Java HotSpot(TM) Server VM (build 21.0-b02-fastdebug, m
ixed mode)
[2011-02-26T09:48:11.10]
[2011-02-26T09:48:11.10] # Test level exit status: 1
[2011-02-26T09:48:11.10]


The above line in the output caught my eye:

> Java HotSpot(TM) Server VM warning: door_call when not enabled

Not sure what that means yet, but it is interesting.