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.
[ JDK VERSION : 1.5.* ] Using an external copy of Tomcat 6.0 with "attach debugger". Setting a breakpoint in a web app gives this message: Not able to submit breakpoint LineBreakpoint AtssAction.java : 354, reason: No executable location available at line 354. Invalid LineBreakpoint AtssAction.java : 354 but line 354 is (split across two lines): messages.add("general", new ActionMessage("error.generic", exc.getMessage())); As soon as I restart Tomcat, the breakpoint badge changes to solid pink, and when I reconnect, there are no errors. The issue occurs only intermittently.
The Sun Javac only creates a location for the first line in multi-line expressions although this is not specified anywhere. Are you using SUN Javac for the compilation? Is the breakpoint toggled at 354 or 355? Thanks.
Please run NetBeans with following option: -J-Dorg.netbeans.modules.debugger.jpda.level=400 and when this happens again, please provide the log file where debugging messages are printed. That should help to identify the problem. If line 354 is the second line of the expression, then the breakpoint will not work there. If line 354 is the first line of the expression, then there should not be any problem. Are you able to submit breakpoints at other lines in that class when it invalidates the breakpoint?
I've also added the class name into the error message, for reference: /shared/data/ccvs/repository/debuggerjpda/src/org/netbeans/modules/debugger/jpda/breakpoints/Bundle.properties,v <-- Bundle.properties new revision: 1.18; previous revision: 1.17 /shared/data/ccvs/repository/debuggerjpda/src/org/netbeans/modules/debugger/jpda/breakpoints/LineBreakpointImpl.java,v <-- LineBreakpointImpl.java new revision: 1.45; previous revision: 1.44
Please try on recent 6.0 build (or upcomming beta2), breakpoints validity works fine for us. If there are still some problems, they should be apparent from extended log generated after -J-Dorg.netbeans.modules.debugger.jpda.level=400 option is used. Resolving as works for me.
Maybe there's really some subtle problem occuring under some specific circumstances. I've found issue #115033.
Resolving as a dupl. of older issue #115033. Please add any further comments/logs there. Thanks. *** This issue has been marked as a duplicate of 115033 ***
Verified ... and Closing all issues resolved into NetBeans 6.7 and earlier.