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.
JSP debugger doesn't select line where it stopped and user can think that it doesn't stop at all. I think it can affect users perception of debugger. That's why I recommend to fix it for NB4.1. To reproduce: - start IDE with empty userdir - open MainTestApplication project (attached) - add breakpoint to index.jsp (e.g. line 18) - start debugger (F5) and wait until it stops at breakpoint - continue (Ctrl+F5) and wait until page is shown in browser - reload page in broser - debugger stops at breakpoint again but green line doesn't appear in the editor Output in Debugger Console is also not accurate. First time when debugger stops at breakpoint the line with 'index.jsp:18' is underlined (link to editor) but second time similar line is not printed out: --- Attaching to tomcat_shared_memory_id User program running Breakpoint reached at line 78 in index.jsp by thread http-8084-Processor19. Thread http-8084-Processor19 stopped at index.jsp:18. Thread http-8084-Processor19 stopped. Thread http-8084-Processor19 stopped. Breakpoint reached at line 18 in index.jsp by thread http-8084-Processor19. --- It started to happen in build 200504142205. From changelogs seems it might be connected to changes for fixing issue 56053.
Created attachment 21836 [details] Project to test.
Workaround is to start debugging of project again (without restarting Tomcat).
Another workaround is to continue with debugging. Next time it is OK. Also you can force Call Stack view to refresh (skip to another view and then back). I can't reproduce it with web project from template. Probably some kind of bigger project has to be debugged.
No more happes because 58091 has been already fixed.
Verified in NB4.1 RC2.