Here is an entry that I had for this test in my
"service_hs nightly analysis 2005.03.09 (final)" report:

New JDI_QUICKLOOK failures (from 2004.12.14)
    nsk/jdi/VirtualMachineManager/connectedVirtualMachines/convm003
        This test timed out waiting for a ThreadDeathEvent on Win32
        Server VM.

        Last failure on 2005.01.19 run with Win32 Server VM.
        Previous failure on 2005.01.08 run with Win32 Server VM.

I think that's enough history for this test.
Here is the UFOYOYO entry that I had for this test in my
"service_hs nightly analysis 2007.02.28 (final)" report:

    nsk/jdi/VirtualMachineManager/connectedVirtualMachines/convm003
        Update: This failure has not reproduced since (at least)
            2006.11.22 which is the date of the oldest results in GTEE.
            I will delete this entry in the next report.

        Last failure on 2005.06.01 run with Win32 Server VM.
        Previous failure on 2005.01.19 run with Win32 Server VM.

Here is the regular entry from my "service_hs nightly analysis
2005.10.03 (final) report that logged the creation of the above
UFOYOYO entry:

New nsk.jdi_quick failures (from 2004.12.14)
    nsk/jdi/VirtualMachineManager/connectedVirtualMachines/convm003
        This test timed out waiting for a ThreadDeathEvent on Win32
        Server VM.

        Update: Copied this entry to the nsk.jdi_quick UFOYOYO section,
            dropped the IA64 failure and dug up the previous failure.
            I will delete this entry in the next report.

        Last failure on 2005.06.08 run with Win-IA64 Server VM.
        Previous failure on 2005.06.01 run with Win32 Server VM.
Here is the entry for this intermittent failure from my
current nightly analysis report:

New nsk.quick_jdi failures (from 2008.01.25)
    nsk/jdi/VirtualMachineManager/connectedVirtualMachines/convm003
        This test failed due to "ERROR: timeout for waiting for a
        ThreadDeathEvent" on Win-AMD64 Server VM (machine
        vm-amd64-03). There used to be a UFOYOYO entry for this test
        that showed a failure on 2005.06.01 run with Win32 Server VM
        and failure on 2005.01.19 run with Win32 Server VM. I deleted
        that entry in the 2007.02.28 report because the failure had not
        reproduced since at least 2006.11.22.

        Last failure on 2008.01.31 with Win32 Client VM (machine vm-amd64-03).
        Previous failure on 2008.01.25 with Win-AMD64 Server VM (machine vm-amd64-03).


Here is a snippet of the .log file from the 2008.01.25 failure:


[2008-01-26T05:14:10.50] Initial VMStartEvent received: VMStartEvent in thread main
[2008-01-26T05:14:10.50] --> debugger: issuspended002a debuggee launched
[2008-01-26T05:14:10.50] --> debugger: 'ready' recieved
[2008-01-26T05:14:10.50]
[2008-01-26T05:14:10.50] ==> nsk/jdi/VirtualMachineManager/connectedVirtualMachines/convm003 TESTING BEGINS
[2008-01-26T05:14:10.50] --> debugger: ......call to Bootstrap.virtualMachineManager()
[2008-01-26T05:14:10.50] --> debugger: ......call to vmm.connectedVirtualMachines()
[2008-01-26T05:14:10.50] --> debugger: connectedVM.size() == 1
[2008-01-26T05:14:10.50] --> debugger: ......getting: VirtualMachine vm1 = connectedVM.get(0);
[2008-01-26T05:14:10.50] --> debugger: ......comparing: vm.equals(vm1)
[2008-01-26T05:14:10.50] --> debugger: ......vm1.dispose()
[2008-01-26T05:14:10.50] --> debugger: waiting for VMDisconnectEvent
[2008-01-26T05:14:10.50] --> debugger: new: eventSet = eventQueue.remove();
[2008-01-26T05:14:10.50] # ERROR: ##> debugger: ERROR: timeout for waiting for a ThreadDeathEvent
[2008-01-26T05:14:11.17] # ERROR: ##> debugger: ERROR: threadDeath != 0
[2008-01-26T05:14:11.17]
[2008-01-26T05:14:11.17] ==> nsk/jdi/VirtualMachineManager/connectedVirtualMachines/convm003 TESTING ENDS
[2008-01-26T05:14:11.17] --> debugger: waiting for the debuggee to finish ...
[2008-01-26T05:14:11.17] --> debugger: debuggee returned expected exit status: 95 == PASS_BASE
[2008-01-26T05:14:11.17] # ERROR: TEST FAILED