resexhausted00[34] fail assert(!thread->owns_locks(), "must release all locks when leaving VM")

New nsk.jvmti failures (from 2007.09.18)
* nsk/jvmti/ResourceExhausted/resexhausted003
        This test failed the following assertion:

            Internal Error (src/share/vm/runtime/interfaceSupport.hpp:263)
            Error: assert(!thread->owns_locks(),
                "must release all locks when leaving VM")

        on Linux AMD64 Server VM (machine vm-v20z-2), Linux IA32 Server
        VM (machine jtg-amd10), and Solaris AMD64 Server VM (machine
        vm-v20z-29).

        This test is covered by the following test bug:

            6601625 4/3 TEST_BUG: UnsatisfiedLinkError in resexhausted001-004
                        on windows-i586

        which does not include this failure mode. This test is on the
        exclude list so I'm not sure why this test was executed, but
        since it revealed a different failure mode that's a good
        thing.
New nsk.jvmti failures (from 2008.12.12)
    nsk/jvmti/ResourceExhausted/resexhausted004
        This test failed the following assertion:

            Internal Error (src/share/vm/runtime/interfaceSupport.hpp:260)
            Error: assert(!thread->owns_locks(),
                "must release all locks when leaving VM")

        on Linux AMD64 Server VM (machine vmnightly6) and Win-AMD64
        Server VM (machine vm-x2200-02). This failure mode is covered
        by the following bug:

            6606767 4/4 resexhausted003 fails assert(!thread->owns_locks(),
                        "must release all locks when leaving VM")

        I will copy this entry to 6606767 and update the synopsis.