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.
Product Version = NetBeans IDE 6.9 Beta (Build 201004200117) Operating System = Windows Vista version 6.0 running on x86 Java; VM; Vendor = 1.6.0_20 Runtime = Java HotSpot(TM) Client VM 16.3-b01 Tried a new JSF WebApplication with JPA (Derby DB). Start it (pressing F6), playing around awhile, then simply closing the IDE. The Glassfish java process is terminated after a while but the other one (I think it's the derby one) is still up and running. Maybe this one should be terminated also like the Glassfish one.
this sounds like a job for the Derby support to resolve...
Same under Linux (Debian Lenny): Linux xxxx 2.6.26-2-amd64 #1 SMP Wed May 12 18:03:14 UTC 2010 x86_64 GNU/Linux java version "1.6.0_12" Java(TM) SE Runtime Environment (build 1.6.0_12-b04) Java HotSpot(TM) 64-Bit Server VM (build 11.2-b01, mixed mode) After having used some Web Application, closing NetBeans closes itself and Glassfish, but not the Derby process; with 'jps -l': 8514 sun.tools.jps.Jps 8389 org.apache.derby.drda.NetworkServerControl
Please, could you reproduce this problem on recent builds of NetBeans 7.1 (http://bits.netbeans.org/download/trunk/nightly/latest/)? If so, describe your steps to reproduce. Thanks
Now both processes are terminated. Steps taken: Open Netbeans (dev201110250600) - File - New Project - Samples - Java Web - JSF JPA (Java EE) - Finish. Then start the app (F6). Play a little around, then close Netbeans.