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.
It was working before that when start GlassFish v3, by default the Derby database will also be started. Steps To Reproduce: 1. Download and install the Beta Candidate build from http://smetiste.czech.sun.com/builds/netbeans/6.8/beta/2009-10-19_20-01-27/ 2. Expand Servers node -> right-click on GlassFish V3, select to start v3 server BUG: The server was started but not the Derby database
1. I am not GFV3 neither Derby expert, but I do not see connection between GFV3 and Derby. Why the database should be started when GFV3 is? 2. Download Ruby edition. Start GFV3. No derby is started or was ever started (how could it, it is not even present). So there is no hard connection between GFV3 and Derby. The fact that it is started in Java edition may be accidental. I do not really think there is anything FoD could do for you. Closing as won'tfix. Feel free to bring this issue to Derby or GFV3 guys, if you disagree with my evaluation.
If user don't want to start V3 servers and Derby database together, he can un-check the option "Start registered Derby Server" in the Server properties panel. With the current behavior, it corrupted the "Start registered Derby Server" option. Please be consistent with the previous functionalities.
The root cause of this issue was probably the change associated with issue 173740...
Steps to reproduce without FoD with older build not containing issue 173740: 1. unzip netbeans/trunk/daily/2009-10-10_02-01-27/zip/netbeans-trunk-nightly-200910100201-ruby.zip 2. netbeans/bin/netbeans --userdir ruby-ud 3. open services tab 4. Add server/GlassFish V3/find it somewhere/install 5. GlassFish v3/Properties => verify option to start Registered Derby Server is on 6. Start the server No Derby server is started. The above indicates that the problem is somewhere else than in FoD and that it is not caused by issue 173740. The interaction between GlassFish and Derby is buggy, issue 173740 just brought the problem to davisn's attention. Reassigning to glassfish. I can help solving the problem, but I need to understand the following: How comes the checkbox "Start registered derby server" is on in Ruby edition? What is the API between glassfish and derby? How actually glassfish locates and triggers derby? Where the API between ideXY/glassfish module and javaUV/derby module is documented? Btw. has such inter cluster API been appropriately reviewed? Where is the code that starts the derby? What shall be proper behaviour of such code in Ruby edition (when Derby is not present)? I am not sure if all these details can be efficiently resolved in IZ, so if you want, let talk about them on Monday.
you raise some good points. getting this corrected correctly seems like it will involve some UI changes that could use some review, etc. The intercluster api is between ideWX/glassfish.common and enterpriseUV/glassfish.javaee and jrubyYZ/glassfish.jruby... they are all friends... Setting the TM to reflect a more realistic commitment.
This may be fixable due to changes related to bug 178802
http://hg.netbeans.org/web-main/rev/0c3ee1082e9a
Integrated into 'main-golden', will be available in build *201004250200* on http://bits.netbeans.org/dev/nightly/ (upload may still be in progress) Changeset: http://hg.netbeans.org/main/rev/0c3ee1082e9a User: vince kraemer <vkraemer@netbeans.org> Log: #175149: derby does not start when GS 3 starts