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 112815 - "Java DB location is not properly set" popup on every server restart
Summary: "Java DB location is not properly set" popup on every server restart
Status: RESOLVED FIXED
Alias: None
Product: db
Classification: Unclassified
Component: Derby (show other bugs)
Version: 6.x
Hardware: Macintosh Mac OS X
: P3 blocker (vote)
Assignee: David Vancouvering
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-08-14 23:17 UTC by _ tboudreau
Modified: 2008-01-26 01:22 UTC (History)
2 users (show)

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
fix for DerbyOptions.trySetLocation (2.00 KB, text/plain)
2007-08-21 19:17 UTC, Vince Kraemer 		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 _ tboudreau 2007-08-14 23:17:59 UTC 
I have Glassfish b58 installed from a download.  Every time I start it I get an annoying dialog saying the Java DB location is not set (JDK 5 on mac).  I know it's 
not set - I also don't care since I'm not using it.

Could this notification be only for the first start of a newly installed appserver, and just be logged in the app startup output thereafter?  It's like punishment 
for using Glassfish.
Comment 1 Vince Kraemer 2007-08-15 21:33:32 UTC 
Do you get this with a clean userdir?

What is the actual text of the message you get?

Have you gone to the Tool->Java DB Database->Settings... dialog and deleted a valid entry?

Please add details and reopen if this is still an issue...
Comment 2 Vince Kraemer 2007-08-15 21:34:06 UTC 
wfm
Comment 3 _ tboudreau 2007-08-15 21:59:41 UTC 
Not a clean userdir.  I rm -Rf'd glassfish b52, installed glassfish b58 with the ant based install script it comes with, and restarted the IDE and added b58 as a 
server.
Comment 4 Vince Kraemer 2007-08-16 00:08:26 UTC 
okay... I assume you put b58 in some directory that said something like /foo/bar/gfb58 and the b52 was in some directory
like /foo/bar/gfb52, right?
Comment 5 _ tboudreau 2007-08-16 02:20:40 UTC 
Yup
Comment 6 Vince Kraemer 2007-08-16 17:33:09 UTC 
ok... I will reopen this and try to duplicate/resolve it.
Comment 7 Vince Kraemer 2007-08-21 01:20:41 UTC 
was able to duplicate.

I check to see if the currently assigned derby install location is a valid directory, when I register an instance.

If the directory doesn't exist, we should be able to reset it... but the DerbySupport.setLocation call seems to be
ignored.  Need some feedback from Andrei about that...
Comment 8 Vince Kraemer 2007-08-21 19:17:42 UTC 
Created attachment 46999 [details]
fix for DerbyOptions.trySetLocation
Comment 10 Vince Kraemer 2007-08-21 19:34:54 UTC 
Please review the patch attached to this issue. After it is applied, this issue will be resolved.

If you want me to apply the patch directly from the build that I created it from, i can do that, too.

Just reassign the issue to me.
Comment 11 David Vancouvering 2008-01-10 00:56:39 UTC 
Vince, sorry this patch never got reviewed.  I'll try to get to it for 6.1.
Comment 12 David Vancouvering 2008-01-26 01:22:12 UTC 
I removed the javadb directory from my Glassfish install, but didn't get an error message.  The Java DB drivers had a
red line through them, and Tools->Java DB showed that you needed to set the location.

But, I applied Vince's changes, and the unit tests pass, and a quick sanity test seems to indicate nothing's broken.  So
I'll apply this as a blind fix and Vince or Tim can verify the issue is fixed.

Checking in DerbyOptions.java;
/cvs/db/derby/src/org/netbeans/modules/derby/DerbyOptions.java,v  <--  DerbyOptions.java
new revision: 1.23; previous revision: 1.22
done