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.
Build: NetBeans IDE 8.0.2 (Build 201411181905) VM: Java HotSpot(TM) 64-Bit Server VM, 25.40-b25, Java(TM) SE Runtime Environment, 1.8.0_40-ea-b23 OS: Mac OS X User Comments: carljmosca: debugging Java Swing application Stacktrace: java.lang.IllegalStateException: can't proxy final class class com.sun.tools.jdi.ClassTypeImpl at com.zeroturnaround.jdi.proxy.DefaultFactory.genProxyBytes(DefaultFactory.java:96) at com.zeroturnaround.jdi.proxy.DefaultFactory.makeProxyClass(DefaultFactory.java:78) at com.zeroturnaround.jdi.proxy.DefaultFactory.<init>(DefaultFactory.java:26) at com.zeroturnaround.jdi.proxy.DefaultFactoryBuilder.newFactory(DefaultFactoryBuilder.java:6) at com.zeroturnaround.jdi.proxy.ProxyFactory.newFactory(ProxyFactory.java:74) at com.zeroturnaround.jdi.proxy.ProxyFactory.getFactory(ProxyFactory.java:66)
Created attachment 152229 [details] stacktrace
Please report to zeroturnaround. This has nothing to do with NetBeans.
If this happened while using JRebel, we can reassign the bug to updatecenters/Plugin Portal so that toomasr@netbeans.org from ZeroTurnaround can take a look at this.
Yes, JRebel was in use. I am also no longer able to debug this particular app; seems to be preventing the debugger from stopping. I have turned off JRebel with no success.
The debugging problem (not stopping on breakpoints) may be specific to Java 1.8.0_40. I changed the to jdk1.8.0_31 and the debugging worked again. Then I changed back to 1.8.0_40 and the breakpoints were once again ignored. Is this an unrelated and/or known issue? Should another bug be filed?
"I have turned off JRebel with no success." Then please report the exception again with JRebel turned off.
I think it should be closed for now...I forgot that 1.8.0_40 is still considered pre-release. I was working on some unrelated stuff and needed to install that version.
I don't think so. The earlier we get the exception stack trace the more time we have for a fix which can be then distributed at least through NetBeans Update Center. Update 40 will go out soon.
Please check this problem in JRebel plugin. There were some changes in JDI in JDK 1.8.0_40.
Sorry for the late reply. There were some internal changes in the 1.8.0_40 version of the JDK. JRebel 6.1.1 fixes the issue (to be released in following weeks), previous versions of JRebel will have this issue with JDK 1.8.0_40. If anybody wants to test before release then let me know and we can do a nightly build.
Created attachment 152678 [details] stacktrace JR-Related problem?
This bug already has 5 duplicates see http://statistics.netbeans.org/exceptions/detail.do?id=215684
Using JR plugin 6.1.1 (verified version, updated from within the IDE) and JDK8_40 my maven-based plugin can be finally debugged. Resolving