Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 7016 - VMDisconnectedException: Got IOException from Virtual Machine when rapidly repeating debug sessions
Summary: VMDisconnectedException: Got IOException from Virtual Machine when rapidly re...
Status: RESOLVED WORKSFORME
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Debug (show other bugs)
Version: 2.0   Edit
Hardware: PC Windows NT
: P3 normal (vote)
Target Milestone: 2.1 RC1   Edit
Assignee: Joe Szurszewski CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2001-12-17 14:53 EST by Knut Radloff CLA
Modified: 2003-02-12 16:20 EST (History)
1 user (show)

See Also:

Attachments
VMDisconnectedException: Got IOException from Virtual Machine (5.11 KB, text/plain)
2001-12-17 14:53 EST, Knut Radloff CLA 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Knut Radloff CLA 2001-12-17 14:53:16 EST 
build 20011206

When I repeatedly start a program in debug mode without waiting between runs I 
get a VMDisconnectedException in PacketReceiveManager.getReply after a few 
restarts (around 5).
If I wait for five seconds after the program terminated before starting it 
again I don't get this exception. Restarting a program in debug mode should 
work regardless of the time since the last debug session.
Note that I restarted by clicking on the debug button.
Here's the simple test case that I ran:

public class PR_ {	
public static void main(String[] args) {
	int[] test2 = new int[] {0, 10, 20, 30, 40, 50, -1};
	
	for (int i = test2.length - 1; i > 1; i--) {
		test2[i] = test2[i - 1];
	}
	for (int i = 0; i < test2.length; i++) {
		System.out.println(test2[i]);
	}	
}
}
Comment 1 Knut Radloff CLA 2001-12-17 14:53:51 EST 
Created attachment 188 [details]
VMDisconnectedException: Got IOException from Virtual Machine
Comment 2 Darin Wright CLA 2002-03-25 10:16:41 EST 
Unable to reproduce. Please re-open if this continues to be a problem for you.
Comment 3 Michael Lupp CLA 2003-01-23 05:13:14 EST 
I get the same exception while debugging with M4, Windows NT and JDK 1.3.1_03.
Comment 4 Darin Wright CLA 2003-01-23 09:23:08 EST 
Needs investigation
Comment 5 Darin Wright CLA 2003-02-07 10:16:19 EST 
Joe, please try to reproduce on M5.
Comment 6 Joe Szurszewski CLA 2003-02-07 17:03:12 EST 
Using M5 on WinXP with JDK 1.4.1 could not duplicate.  Tried rapidly clicking 
Beetle button and simply holding down F11, and am amble to perform several dozen 
launches without incident.  Will try other VMs.
Comment 7 Joe Szurszewski CLA 2003-02-07 17:11:27 EST 
Tried several other VMs, including JDK1.3.1 with no luck.  Michael, are you able 
to reproduce this problem with M5?  If so, can you provide a simple test case?  
Thanks.
Comment 8 Joe Szurszewski CLA 2003-02-12 16:20:44 EST 
Noticed that stack trace appears to from J9.  Tried to reproduce on J9 with no 
luck.  Marking as WORKSFORME since I can't duplicate the problem.  Knut & 
Michael, please reopen if you can reproduce this on M5 or later.