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.
Very often debugger cannot attach to sun application server. It gets stuck in the middle of debug action but IDE is alive. To reproduce: - run IDE with empty userdir - add Sun App. server in Runtime view - create web application project from template - add breakpoint at index.jsp (e.g. line 18) - start debugger (F5). Server is started, debugger is started but it never reaches the breakpoint. If it works try to stop debugger and start it again. I will attach thread dump and other logs. Debugger console prints Attaching to localhost:9009 Attaching to localhost:9009 or User Program Running User Program Running Build NB5.0 Beta 200509251930 or NB dev 20050926-0457, JDK1.5.0_05, WindowsXP, sjsas_pe-8_1_02_2005Q2-b11.
Created attachment 25178 [details] Thread dump
Created attachment 25179 [details] Server log
Created attachment 25180 [details] Contents of output window.
Workaround is to reload page in browser or restart debugger.
The debugger doesn't work only for Sun App server (with Tomcat we can't reproduce it). I'm reassign issue to sunappserv8 to evaluate.
does it work with jdk1.5.04? When you see: Attaching to localhost:9009 Attaching to localhost:9009 or User Program Running User Program Running" did you debug twice or only once? this is important: the plugin does not control these messages emitted by the debugger. Maybe the debugger is starting twice? You describe the workaround to reload the index page: does it work all the time, i.e the brkpoint is then reached?
Cannot reproduce with JDK1.5.04 I updraged also AS and nb to jdk1.5.)5, and still cannot reproduce. Petr Blaha, can you confirm you can reproduce this state? Please attach the domain.xml of this server for analysis.
Hi Ludo, I can't reproduce the issue on Linux neither on Win XP machine with the latest beta build and mentioned jdk. I asked Jirka for testing this more thoroughly and try to find some reproducible case. He was trying to show me the issue on Win XP box and after starting debug session several time he got this issue. He started debugger (press F5) in very short sequence and he didn't get warning message about raunning other debugg session. However, then the issue disappeared :-(. I suggest to mark the issue as RANDOM.
It seems to be a problem in debugger JPDA. Debugger states were not fired accurately. I tried to patch StartActionProvider.java and then it worked without problems. I asked guys from debugger team to review my changes and integrate them if it is correct.
Created attachment 25233 [details] Proposed patch
Should be fixed (thanks to Jirka Skrivanek): Checking in StartActionProvider.java; /cvs/debuggerjpda/src/org/netbeans/modules/debugger/jpda/actions/StartActionProvider.java,v <-- StartActionProvider.java new revision: 1.20; previous revision: 1.19 done
Verified in build 20050928-1818.