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 58781 - VMDisconnectedException at JPDAThreadImpl.getStackDepth():249
Summary: VMDisconnectedException at JPDAThreadImpl.getStackDepth():249
Status: VERIFIED FIXED
Alias: None
Product: debugger
Classification: Unclassified
Component: Java (show other bugs)
Version: 5.x
Hardware: All All
: P3 blocker (vote)
Assignee: issues@debugger
URL:
Keywords: THREAD
Depends on: 58827
Blocks:
  Show dependency tree
 
Reported: 2005-05-11 13:47 UTC by Martin Schovanek
Modified: 2007-01-18 08:34 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments
VMDisconnectedException (1.06 KB, text/plain)
2005-05-11 13:49 UTC, Martin Schovanek
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Martin Schovanek 2005-05-11 13:47:24 UTC
[#200505101800, jdk1.5.0]

The exception is thrown by web poject automated test, one scenario is:
1) run Debug File on a .jsp
NOTE: web app stops at brakpoint
2) press continue
3) finish debugger

Manually I cannot reproduce it. But on my Mac OS X I got it when:
1) create new Web Project
2) run Debug Project
3) press Pause in the Debugger Toolbar
Cannot reproduce on my Linux workstation.
Comment 1 Martin Schovanek 2005-05-11 13:49:51 UTC
Created attachment 22097 [details]
VMDisconnectedException
Comment 2 Max Sauer 2005-05-11 13:56:50 UTC

*** This issue has been marked as a duplicate of 58769 ***
Comment 3 Martin Schovanek 2005-05-16 09:59:21 UTC
REOPENED - the issue #58769 is fixed but automated tests still throw the
VMDisconnectedException.
Comment 4 Martin Schovanek 2005-05-16 10:26:26 UTC
REOPENED - the issue #58769 is fixed but automated tests still throw the
VMDisconnectedException.
Comment 5 Martin Entlicher 2005-05-16 17:58:09 UTC
This likely depends on issue #58827. Automated tests can trigger something which
is nearly unreproducible manually. This is most probably a threading issue.
Comment 6 Martin Entlicher 2005-06-02 14:36:44 UTC
This is comming from PopToHereActionProvider. It should be fixed after latest
fixes of issue #58769 and #58827.
Comment 7 Martin Schovanek 2007-01-18 08:34:34 UTC
v.