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.
This bug was originally marked as duplicate of bug 228820, that is already resolved. This bug is still valid, so this seems to be another bug, but it might be related. Build: NetBeans IDE Dev (Build 20130617-0535597d537f) VM: Java HotSpot(TM) 64-Bit Server VM, 23.21-b01, Java(TM) SE Runtime Environment, 1.7.0_21-b11 OS: Linux User Comments: janario: In debug when I try to inspect an expression, selecting and putting cursos to see the value. rodrigorsantos: <Please provide a description of the problem or the steps to reproduce> janario: debugging janario: Selecting a block to inspect in debug rodrigorsantos: <Please provide a description of the problem or the steps to reproduce> janario: debuging Stacktrace: com.sun.jdi.VMMismatchException: instance of org.apache.tomcat.util.threads.TaskThread(name='http-bio-8080-exec-15', id=12) at com.sun.tools.jdi.MirrorImpl.validateMirror(MirrorImpl.java:68) at com.sun.tools.jdi.ObjectReferenceImpl.invokeMethod(ObjectReferenceImpl.java:365) at org.netbeans.modules.debugger.jpda.jdi.ObjectReferenceWrapper.invokeMethod(ObjectReferenceWrapper.java:510) at org.netbeans.modules.debugger.jpda.expr.TreeEvaluator.invokeVirtual(TreeEvaluator.java:265) at org.netbeans.modules.debugger.jpda.JPDADebuggerImpl.invokeMethod(JPDADebuggerImpl.java:1060) at org.netbeans.modules.debugger.jpda.JPDADebuggerImpl.invokeMethod(JPDADebuggerImpl.java:1007)
Created attachment 136047 [details] stacktrace
Some concrete steps to reproduce would help. I'm not able to reproduce this so far... Do you have more than one debugging session running when this occurs?
Integrated into 'main-silver', will be available in build *201306272300* on http://bits.netbeans.org/dev/nightly/ (upload may still be in progress) Changeset: http://hg.netbeans.org/main-silver/rev/0674eb866cb3 User: mentlicher@netbeans.org Log: Some logging added to explore issue #231541.
Integrated into 'main-silver', will be available in build *201308012300* on http://bits.netbeans.org/dev/nightly/ (upload may still be in progress) Changeset: http://hg.netbeans.org/main-silver/rev/fbdeebfc94db User: mentlicher@netbeans.org Log: Logging improved to explore issue #231541.
*** Bug 232240 has been marked as a duplicate of this bug. ***
Created attachment 144244 [details] stacktrace Attempting to debug a web application.
Created attachment 144246 [details] stacktrace Attempting to debug a web application.
It's really interesting, that there happens to be created two instances of VirtualMachineImpl, but they have the same System.identityHashCode(). From the log we see that their .toString() is the same. It's really strange, that in all reports, they consistently have the same identity hash code, but they are not equal in '==' sense. It looks very strange.
I am using JRebel with my application. When the agent is removed, it does not produce the same exception.
Thanks. Thus it looks to be JRebel-specific. I've added some more logging... changeset: 270996:4fd50f140b46
Integrated into 'main-silver', will be available in build *201401240001* on http://bits.netbeans.org/dev/nightly/ (upload may still be in progress) Changeset: http://hg.netbeans.org/main-silver/rev/4fd50f140b46 User: mentlicher@netbeans.org Log: #231541: More extensive logging added when there appears two instances of VirtualMachineImpl.
*** Bug 235741 has been marked as a duplicate of this bug. ***
(In reply to jyeary from comment #9) > I am using JRebel with my application. When the agent is removed, it does > not produce the same exception. For me it is different. Application uses JR agent 5.5.2 (yes I have to update) and IDE uses JR plugin 5.6.0. When I deactivate the JR plugin in NB (and keep the agent for the application), the error is gone.
@Martin: I looked it up in my mails. It should be fixed in the JRebel plugin by Lauri Tulmin from ZT in version >=5.6.4 So I close it as resolved. Thanks for your help. In the worst case I will reopen this issue.