This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.

Bug 136628 - VMDisconnectedException: connection is closed
Summary: VMDisconnectedException: connection is closed
Status: VERIFIED DUPLICATE of bug 129390
Alias: None
Product: debugger
Classification: Unclassified
Component: Java (show other bugs)
Version: 6.x
Hardware: All All
: P3 blocker (vote)
Assignee: issues@debugger
URL: http://statistics.netbeans.org/except...
Keywords:
Depends on:
Blocks:
 
Reported: 2008-06-06 09:52 UTC by pribyl
Modified: 2008-06-24 09:34 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter: 62666

Attachments
stacktrace (5.85 KB, text/plain)
2008-06-06 09:52 UTC, pribyl 		Details
stacktrace (2.44 KB, text/plain)
2008-06-10 11:06 UTC, kate 		Details
stacktrace (2.43 KB, text/plain)
2008-06-13 13:36 UTC, kate 		Details
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 pribyl 2008-06-06 09:52:34 UTC 
Build: NetBeans IDE Dev (Build 200806060005)
VM: Java HotSpot(TM) Client VM, 11.0-b11, Java(TM) SE Runtime Environment, 1.6.0_10-beta-b20
OS: Windows XP, 5.1, x86

User Comments: 
I just run debugger on a simple java project.
The debugger works just fine, but this exception keeps poping up every time i run the debugger. Restarting IDE and/or deleting the usredir does not help.
(it started with the latest NB build)
Comment 1 pribyl 2008-06-06 09:52:39 UTC 
Created attachment 62451 [details]
stacktrace
Comment 2 kate 2008-06-10 11:06:53 UTC 
Created attachment 62605 [details]
stacktrace
Comment 3 kate 2008-06-13 13:36:09 UTC 
Created attachment 62811 [details]
stacktrace
Comment 4 David Simonek 2008-06-17 16:27:03 UTC 
Passing to debugger, real cause is
com.sun.jdi.VMDisconnectedException: connection is closed
        at com.sun.tools.jdi.TargetVM.send(TargetVM.java:274)
        at com.sun.tools.jdi.VirtualMachineImpl.sendToTarget(VirtualMachineImpl.java:1011)
        at com.sun.tools.jdi.PacketStream.send(PacketStream.java:41)
        at com.sun.tools.jdi.JDWP$EventRequest$Set.enqueueCommand(JDWP.java:6765)
        at com.sun.tools.jdi.JDWP$EventRequest$Set.process(JDWP.java:6735)
        at com.sun.tools.jdi.EventRequestManagerImpl$EventRequestImpl.set(EventRequestManagerImpl.java:179)
        at com.sun.tools.jdi.EventRequestManagerImpl$EventRequestImpl.setEnabled(EventRequestManagerImpl.java:143)
        at com.sun.tools.jdi.EventRequestManagerImpl$EventRequestImpl.enable(EventRequestManagerImpl.java:128)
        at org.netbeans.modules.debugger.jpda.models.ThreadsCache.setVirtualMachine(ThreadsCache.java:101)
Comment 5 Martin Entlicher 2008-06-17 16:33:16 UTC 
Duplicate of issue #129390.
However, we must no call JDI methods from AWT, it can block the UI.
The stack trace shows path from
org.netbeans.modules.debugger.jpda.ui.debugging.DebuggingView.componentShowing(DebuggingView.java:359) to
org.netbeans.modules.debugger.jpda.JPDADebuggerImpl.getAllThreads(JPDADebuggerImpl.java:1317) and to
com.sun.tools.jdi.EventRequestManagerImpl$EventRequestImpl.enable(EventRequestManagerImpl.java:128)
This must be put off the AWT.
Comment 6 Martin Entlicher 2008-06-18 13:58:26 UTC 
JDI methods are not called from AWT in this case: http://hg.netbeans.org/main/rev/05b903392029
Resolving as a duplicate of #129390.

*** This issue has been marked as a duplicate of 129390 ***
Comment 7 pribyl 2008-06-24 09:34:41 UTC 
Verified

I am sorry for the duplicate