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 217048 - com.sun.jdi.InvocationException: Exception occurred in target VM
Summary: com.sun.jdi.InvocationException: Exception occurred in target VM
Status: RESOLVED DUPLICATE of bug 222288
Alias: None
Product: debugger
Classification: Unclassified
Component: Java (show other bugs)
Version: 7.2
Hardware: All All
: P3 normal (vote)
Assignee: Martin Entlicher
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-08-17 20:26 UTC by rhinoguy
Modified: 2012-11-19 14:51 UTC (History)
4 users (show)

See Also:
Issue Type: DEFECT
Exception Reporter: 183135


Attachments
stacktrace (1.39 KB, text/plain)
2012-08-17 20:26 UTC, rhinoguy
Details
stacktrace (1.39 KB, text/plain)
2012-11-13 22:59 UTC, Chiana
Details
stacktrace (1.39 KB, text/plain)
2012-11-13 23:05 UTC, Chiana
Details
stacktrace (1.39 KB, text/plain)
2012-11-15 07:04 UTC, Chiana
Details

Note You need to log in before you can comment on or make changes to this bug.
Description rhinoguy 2012-08-17 20:26:00 UTC
Build: NetBeans IDE 7.2 (Build 201207171143)
VM: Java HotSpot(TM) Client VM, 23.2-b09, Java(TM) SE Runtime Environment, 1.7.0_06-b24
OS: Windows 7

User Comments:
ruol: error occurred while attaching Java Debugger (JPDA) via SocketAttach

GUEST: Breakpoint just activated

rhinoguy: Attaching the debugger to an existing applet.

GUEST: trying to launch 3D java api ColorCube.java sample to test if applet can be run with netbeans and these jnlp launcher

ruol: Error occured while attaching debugger via NetBeans attach menu item ... Java Debugger (JPDA) using Connector: SocketAttach (Attaches by socket to other VMs).

GUEST: attaching the debugger




Stacktrace: 
com.sun.jdi.InvocationException: Exception occurred in target VM
   at com.sun.tools.jdi.ClassTypeImpl.invokeMethod(ClassTypeImpl.java:246)
   at org.netbeans.modules.debugger.jpda.jdi.ClassTypeWrapper.invokeMethod(ClassTypeWrapper.java:280)
   at org.netbeans.modules.debugger.jpda.visual.VisualDebuggerListener.initDebuggerRemoteService(VisualDebuggerListener.java:298)
   at org.netbeans.modules.debugger.jpda.visual.VisualDebuggerListener.access$100(VisualDebuggerListener.java:122)
   at org.netbeans.modules.debugger.jpda.visual.VisualDebuggerListener$2.breakpointReached(VisualDebuggerListener.java:185)
   at org.netbeans.api.debugger.jpda.JPDABreakpoint.fireJPDABreakpointChange(JPDABreakpoint.java:293)
Comment 1 rhinoguy 2012-08-17 20:26:03 UTC
Created attachment 123269 [details]
stacktrace
Comment 2 Quality Engineering 2012-10-09 02:06:36 UTC
Integrated into 'main-golden', will be available in build *201210090002* on http://bits.netbeans.org/dev/nightly/ (upload may still be in progress)
Changeset: http://hg.netbeans.org/main-golden/rev/907fe0b98f13
User: mentlicher@netbeans.org
Log: #217048: Log the target exception.
Comment 3 Chiana 2012-11-13 22:59:32 UTC
Created attachment 127745 [details]
stacktrace

Tried to debug an RMI server. Just installed 20121113 after uninstalling 1108 keeping configuration
Comment 4 Chiana 2012-11-13 23:05:32 UTC
Created attachment 127747 [details]
stacktrace

Seems debugger is unusable...
Comment 5 Martin Entlicher 2012-11-14 14:20:26 UTC
I believe, that debugger should continue fine after this exception occurs. My apologies for the problem in the code, which should log the actual target exception, that has occurred. After the fix of issue #222077 gets propagated into a dev build, please try this again. The real cause of this issue should be logged. Thanks.
Comment 6 Chiana 2012-11-15 07:04:30 UTC
Created attachment 127830 [details]
stacktrace

Starting debug session with 121115 and standard security manager installed.
Comment 7 Chiana 2012-11-15 07:10:23 UTC
Martin, I believe it does not, it seems to loose grip of the active process and the program continues without debugging or just sits on a breakpoint without beeing able to resume because the controls are inactivated.
Comment 8 Martin Entlicher 2012-11-19 14:51:50 UTC
Thanks to issue #222288 I know now what is the problem.
Your SecurityManager does not allow to listen for all AWT events, which is used by visual debugging. We need to handle this gracefully and assure that the debugger can continue.

I'm resolving this as a duplicate of issue #222288, since it contains the real cause after the logging was improved.

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