Bug 66334 - Remote Debug Connection not disconnected when JDIDebugModel.newDebugTarget(...) fails
Summary: Remote Debug Connection not disconnected when JDIDebugModel.newDebugTarget(.....
Status: RESOLVED DUPLICATE of bug 66330
Alias: None
Product: Platform
Classification: Eclipse Project
Component: Debug (show other bugs)
Version: 3.0   Edit
Hardware: PC Windows XP
: P3 critical (vote)
Target Milestone: ---   Edit
Assignee: Platform-Debug-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords: core
Depends on:
Blocks:
 
Reported: 2004-06-09 11:44 EDT by Richard Birenheide CLA
Modified: 2004-06-09 11:47 EDT (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Richard Birenheide CLA 2004-06-09 11:44:23 EDT
In the method SocketAttachConnector.connect(....) a virtual machine is created 
by 
VirtualMachine vm = connector.attach(map);
This obviously connects to the remote debug process. If the subsequent call to 
debugTarget= JDIDebugModel.newDebugTarget(launch, vm, vmLabel, null, 
allowTerminate, true);
fails (eg. by a time-out), the connection to the remote VM is not terminated 
leaving the debug port of the remote VM blocked. Since there is no means to get 
the associated VirtualMachine object I can cannot do this in my 
LaunchConfigurationDelegate. Either there should be a method getVm(): 
VirtualMachine in the IVMConnector interface or you catch all Throwables and 
release the connection on catching the error (eventually in method abort()).

Cheers
Richard
Comment 1 Darin Wright CLA 2004-06-09 11:47:59 EDT

*** This bug has been marked as a duplicate of 66330 ***