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 167337 - Can't Kill a process
Summary: Can't Kill a process
Status: RESOLVED DUPLICATE of bug 135475
Alias: None
Product: projects
Classification: Unclassified
Component: Maven (show other bugs)
Version: 6.x
Hardware: PC All
: P3 blocker (vote)
Assignee: Milos Kleint
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-06-18 21:17 UTC by bkreider
Modified: 2009-06-23 16:36 UTC (History)
2 users (show)

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
Project that recreates error (249.07 KB, text/plain)
2009-06-19 18:16 UTC, bkreider 		Details
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description bkreider 2009-06-18 21:17:02 UTC 
Easy to recreate:

Create a Frame Form and add a jlabel.  Make the jlabel look up a resource bundle property that doesn't exist.  Run the
file and you will receive an error but the application will not shut down.  On the bottom of the IDE you can see the
process still running, click the kill process button and a confirmation dialog will come up asking if you want to cancel
the process.  Hit yes in the confirmation dialog box.  Verify that the process is still running.

The only way I could kill the process was to go to the task manager in windows and kill the process there.
Comment 1 Tomas Pavek 2009-06-19 13:38:57 UTC 
If I follow your steps (create JFrame, added JLabel with reference to non-existing bundle), I get an exception like:
java.util.MissingResourceException: Can't find bundle for base name app1/Bundle
        at java.util.ResourceBundle.throwMissingResourceException(ResourceBundle.java:1521)
        at java.util.ResourceBundle.getBundleImpl(ResourceBundle.java:1260)
        at java.util.ResourceBundle.getBundle(ResourceBundle.java:715)
        at app1.NewJFrame.initComponents(NewJFrame.java:40)
        at app1.NewJFrame.<init>(NewJFrame.java:22)
        at app1.NewJFrame$1.run(NewJFrame.java:54)
        at java.awt.event.InvocationEvent.dispatch(InvocationEvent.java:209)
        at java.awt.EventQueue.dispatchEvent(EventQueue.java:597)
        at java.awt.EventDispatchThread.pumpOneEventForFilters(EventDispatchThread.java:284)
        at java.awt.EventDispatchThread.pumpEventsForFilter(EventDispatchThread.java:184)
        at java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:174)
        at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:169)
        at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:161)
        at java.awt.EventDispatchThread.run(EventDispatchThread.java:122)

But the process ends - because exception causes the form creation failure, so without a main window the app exists 
after leaving 'main'.

I've changed the form so it is created but fails in setVisible. Then I get the process running and visible in IDE 
status bar, but if I select to kill it, it is killed successfully.

Can you pleasse attach the exact form (or entire project) on which you can reproduce the problem? And also please 
attach IDE log file after you try to kill the process unsuccessfully (menu View | IDE Log).
Comment 2 bkreider 2009-06-19 18:16:02 UTC 
Created attachment 83825 [details]
Project that recreates error
Comment 3 bkreider 2009-06-19 18:25:27 UTC 
I added an attachment that can recreate this problem in 6.7 RC3.  The file you will need to run is MainFrame.  Another
thing that occurred to me, my projects are Maven projects and that could have something to do with this.  The project I
attached is also a Maven project.  I also added the IDE log in the logs directory along with screen shots of the process
tree during each stage.
Comment 4 Tomas Pavek 2009-06-22 16:59:36 UTC 
I can reproduce it with attached project. Can kill from NetBeans, but it leaves java process behind.

This might be a maven project support issue, reassigning...
Comment 5 Milos Kleint 2009-06-23 14:15:07 UTC 
duplicate of #135475

*** This issue has been marked as a duplicate of 135475 ***
Comment 6 Jaroslav Pospisil 2009-06-23 16:36:04 UTC 
Matching priority to original issue.