Product Version = NetBeans IDE Dev (Build 201209190001)
Operating System = Windows XP version 5.1 running on x86
Java; VM; Vendor = 1.7.0_07
Runtime = Java HotSpot(TM) Client VM 23.3-b01

(copied from my mail, currently double-checked within NB)

Suspect: Debugging WebApp, stopping this app, stopping server, exist NB: Exiting IDE will stop debugging. Worth to create an issue.

"Michael Müller" <michael.mueller@mueller-bruehl.de> hat am 19. September 2012 um 11:48 geschrieben:
> Hi,
>  
> I have a JEE web app. For debugging purpose, I'll start with Ctrl-F5. So far, everything is fine.
>
> Sometimes, after some edits, I'll restart it in debug mode, without stopping the prior session (ok, never forget to stop a debug session).  In former versions of NB there had been no problems. It seemd NB stoped the running process and replaced it by the new debug session.
>  
> Now, when closing the IDE NB wars this will stop some running sessions. It seems, NB allways spawns a new debug session now. But, once I started a new seesion without stopping the old one, pressing Shift-Ctrl-F5 will terminate the current debug session.
>  
> How can I stop the old session?
> One trick ist to start something eles to force the display of running processes, on the right side of the bottom status line. I can open and terminate a running process there. But if this window is absent, how can I display all running (background) processes to control them?
> And BTW, it might be usefull to start a couple of debug sessions. I used this to inspect some different projects. But does this make sence to start multiple debug sessions for just one project? In case of a web app changed source will force a re-deploy. Thus I can't really debug in an old session. INHO at least for a web project, it's senceless to start multiple debug sessions. In this case I prefer the former behaviour of NB.
>  
> How do you think about this?
>  
> Best,
> Michael