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.
Summary: | Persistent breakpoint at java.lang.Throwable with jrebel | ||
---|---|---|---|
Product: | javaee | Reporter: | everflux <everflux> |
Component: | Debugger | Assignee: | Martin Entlicher <mentlicher> |
Status: | VERIFIED WORKSFORME | ||
Severity: | normal | ||
Priority: | P3 | ||
Version: | 7.4 | ||
Hardware: | PC | ||
OS: | Linux | ||
Issue Type: | DEFECT | Exception Reporter: |
Description
everflux
2013-08-04 14:16:36 UTC
BTW: I have removed all breakpoints and made sure that I did not have any set at java.lang.Throwable. This is not a debugger problem. The stacktrace refers to Hibernate/Spring integration in JRebel. Please report this issue to JRebel forum (if you haven't yet). Reported to zt at http://zeroturnaround.com/forums/topic/debugger-issue-with-netbeans-a-null-plugin-while-handling-a-class-reload-event/ @everflux: Please provide a detailed jrebel.log. See http://zeroturnaround.com/forums/topic/debugger-issue-with-netbeans-a-null-plugin-while-handling-a-class-reload-event/#post-35538 Please check Tools -> Options -> Java -> Java Debugger -> General -> "Stop on uncaught exceptions" option. It's likely checked on, unchecking this should solve the exception breakpoint problem. "schema change not implemented" likely means, that the next option "Apply code changes after save" is also turned on. Debugger is then trying to apply code changes in JVM, which does not support schema changes. Since it does not have sense when you use JRebel, turn this off. These options should solve this issue. Awesome, thank you very very much! Works great with jrebel+tomcat+netbeans 7.4rc1 (I did not use the jrebel plugin, but configured the apache platform arguments) Thanks for confirmation. |