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.

Bug 50849

Summary: Can't debug WebApp - no browser opened, no breakpoint reached
Product: debugger Reporter: zikmund <zikmund>
Component: JavaAssignee: issues@debugger <issues>
Status: CLOSED DUPLICATE    
Severity: blocker    
Priority: P1    
Version: 4.x   
Hardware: PC   
OS: All   
Issue Type: DEFECT Exception Reporter:

Description zikmund 2004-10-26 13:17:47 UTC
Build 200410251800

1) Run IDE with clean user dir
2) Create new WebApp project
3) Set a breakpoint to JSP
4) Run debugger (F5)
5) ERROR:
URL is not opended in browser, manual URL typing
doesn't reach set breakpoint.

Notice: There are no any reported problems in
output windows until you stop debug session
(Shift-F5) - there's a
org.netbeans.api.debugger.jpda.DebuggerStartException
in debug output then.
Comment 1 L Martinek 2004-10-26 13:25:31 UTC
It happens on all platforms. Automated tests discovered that build
200410202002 is OK, but build 200410241800 is bad.
Comment 2 L Martinek 2004-10-26 13:33:27 UTC
"MyWebModule (debug)" output contains this:

init:
deps-jar:
compile:
compile-jsps:
debug:
Starting debug server Bundled Tomcat (5.0.28)
Tomcat server started.
Incrementally deploying http://localhost:8084/WebApplication9
Completed incremental distribution of
http://localhost:8084/WebApplication9


It doesn't contains BUILD SUCCESSFUL/FAILED, its probably somewhere stuck.
Comment 3 Martin Grebac 2004-10-26 13:43:27 UTC
Right, and debugger output contains just this line: 
"Attaching to localhost:11555" - and debugger does not create
connection  - even when I try to Attach to remote process manually
through menu I get the same problem -> reassigning. 
I've seen some commit to StartActionProvider on Friday (maybe related)?
Comment 4 Maros Sandor 2004-10-26 16:20:23 UTC

*** This issue has been marked as a duplicate of 50825 ***
Comment 5 zikmund 2004-10-27 10:06:05 UTC
Verified fix in build 200410261800.