ThreadInfo.getLockedMonitors doesn't include monitors locked by JNI MonitorEnter function.
Keeping track of the stack frame and depth of each JNI MonitorEnter would have performance impact. The spec should be fixed to special case monitors locked by JNI function.
The following tests (which will be included in VM testbase 1.6r06) fail because to this:
nsk/monitoring/ThreadMXBean/ThreadInfo/LockingThreads/LockingThreads001
nsk/monitoring/ThreadMXBean/ThreadInfo/LockingThreads/LockingThreads002
nsk/monitoring/ThreadMXBean/ThreadInfo/LockingThreads/LockingThreads003
nsk/monitoring/ThreadMXBean/ThreadInfo/LockingThreads/LockingThreads004
nsk/monitoring/ThreadMXBean/ThreadInfo/LockingThreads/LockingThreads005
nsk/monitoring/ThreadMXBean/ThreadInfo/Multi/Multi001
nsk/monitoring/ThreadMXBean/ThreadInfo/Multi/Multi002
nsk/monitoring/ThreadMXBean/ThreadInfo/Multi/Multi003
nsk/monitoring/ThreadMXBean/ThreadInfo/Multi/Multi004
nsk/monitoring/ThreadMXBean/ThreadInfo/Multi/Multi005
nsk/monitoring/ThreadMXBean/ThreadInfo/Deadlock/NativeDeadlock001
nsk/monitoring/ThreadMXBean/ThreadInfo/Deadlock/MixedDeadlock001