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.
Summary: | Stop Application does not work anymore | ||
---|---|---|---|
Product: | groovy | Reporter: | bennyv <bennyv> |
Component: | Grails | Assignee: | schmidtm <schmidtm> |
Status: | VERIFIED FIXED | ||
Severity: | blocker | ||
Priority: | P3 | ||
Version: | 6.x | ||
Hardware: | PC | ||
OS: | Windows XP | ||
Issue Type: | DEFECT | Exception Reporter: |
Description
bennyv
2008-02-29 08:54:26 UTC
stopping the running grails server end's up in a call to java.lang.Process.destroy(). This works fine for Linux and Mac OSX (JDK 1.5). Nevertheless i can confirm that it doesn't work for Windows. It probably slipped our attention, that it never worked on this platform. Stay tuned for more investigations. Ok, here's my status report on this pretty nasty issue: a) It's reproducable on JDK6 as well b) Process.destroy() never worked, since we are dealing with a process group: Netbeans - cmd.exe (grails.bat) - java.exe This is explained in great detail here: (process) Process.destroy does not kill multiple child processes http://bugs.sun.com/view_bug.do?bug_id=4770092 c) Possible solutions/workarounds (not sure whether they are actually feasable) 1.) try to find the right org.codehaus.groovy.grails.cli.support.GrailsStarter java program using windows (onboard) tools like: wmic, tasklist and kill them using: taskkill 2.) Try to exclude the grails.bat startup-script altogether and start java/w.exe directly. These two options have to be carefully discussed and evaluated. This is (hopefully) now fixed: http://hg.netbeans.org/main/contrib/rev/fa372d350cd2 Someone with Vista should verify. Integrated into 'main-golden', available in NB_Trunk_Production #206 build Changeset: http://hg.netbeans.org/main/rev/48fda0407ff6 User: Matthias Schmidt <schmidtm@netbeans.org> Log: Fix for #128790, solution for Windows XP+ using wmic.exe and taskkill v. |