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.
Created attachment 135213 [details] Web application for reproducing bug. 1. Open attached web application. 2. Run web application with GlassFish 4 and wait for browser to open and display. 3. Click red X Exit button to exit IDE. 4. Dialog pops up--Exit the IDE will terminate the following process: Process - WebApplication1(run) (See attached screenshot) 5. Click Cancel 6. Click red X Exit button to exit IDE. NetBeans will not exit. Expected: No dialog box should popup and IDE should exit. Workaround: Kill Process. Product Version: NetBeans IDE Dev (Build 201305312301) Java: 1.7.0_21; Java HotSpot(TM) 64-Bit Server VM 23.21-b01 Runtime: Java(TM) SE Runtime Environment 1.7.0_21-b11 System: Windows 7 version 6.1 running on amd64; Cp1252; en_US (nb)
Created attachment 135214 [details] logfile
Created attachment 135215 [details] Screenshot of popup dialog
This is the expected behavior. Clicking Cancel or closing the dialog box aborts the Exit.
(In reply to comment #3) > This is the expected behavior. Clicking Cancel or closing the dialog box aborts > the Exit. That is fine, but if I cancel the dialog box, NetBeans will not Exit and I have to kill the process.
(In reply to comment #4) > That is fine, but if I cancel the dialog box, NetBeans will not Exit and I have > to kill the process. So, after first exit invocation and cancelling it, you invoke exit again? What exactly happens after the second invocation of File/Exit?
(In reply to comment #5) > (In reply to comment #4) > > That is fine, but if I cancel the dialog box, NetBeans will not Exit and I have > > to kill the process. > > So, after first exit invocation and cancelling it, you invoke exit again? What > exactly happens after the second invocation of File/Exit? Nothing, Exit does not work if I use File>>Exit or Click the upper left Red X button on the main NetBeans window afterward.
*** This bug has been marked as a duplicate of bug 230452 ***