Following nsk tests fails intermittently.

   nsk/jdi/stress/serial/monitorEvents002
        This test failed an assertion Linux IA32 Client VM (machine
        em64t-002); see addClassFilter_ReferenceType entry below.


   nsk/jdi/MonitorContendedEnteredRequest/addClassFilter_ReferenceType
        This test failed the following assertion:

            Internal Error (src/share/vm/runtime/jniHandles.hpp:185)
            Error: assert(handle != 0,"JNI handle should not be null")

        on Solaris SPARC Client VM (machine sys-ldom1-06). This failure
        mode matches an entry in the following bug:
Another test failing this assertion in nightly:

New nsk.quick-jdi failures (from 2008.09.17)
    nsk/jdi/stress/serial/monitorEvents001
        This test failed an assertion Solaris SPARC Server VM (machine
        toasteroven); see addClassFilter_ReferenceType entry below.
Another test failing this assertion in nightly:

New nsk.quick-jdi failures (from 2008.12.18)
    nsk/jdi/MonitorContendedEnterRequest/addClassFilter_ReferenceType
        This test failed the following assertion on Linux IA32 Server
        VM (machine vm-v20z-1):

            Internal Error (src/share/vm/runtime/jniHandles.hpp:185)
            Error: assert(handle != __null,"JNI handle should not be null")

        This failure mode is covered by the following bug:

            6749729 3/4 fastdebug vm crashes due to bad jni handle passed
                        from backend when monitor events are enabled.

        I will copy this entry to 6749729.