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 113910 - Connection error dialog for Derby connections needs more info
Summary: Connection error dialog for Derby connections needs more info
Status: RESOLVED WONTFIX
Alias: None
Product: db
Classification: Unclassified
Component: Derby (show other bugs)
Version: 6.x
Hardware: PC All
: P4 blocker (vote)
Assignee: Jiri Rechtacek
URL:
Keywords:
Depends on:
Blocks: 152765
  Show dependency tree
 
Reported: 2007-08-27 22:30 UTC by John Baker
Modified: 2009-09-21 13:22 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
diff of fix (1.16 KB, text/plain)
2007-11-02 09:11 UTC, John Baker 		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 John Baker 2007-08-27 22:30:47 UTC 
When attempting to connect to an existing, registered Derby connection  and the connection fails
then an error dialog opens.

"Unable to connect.  Cannot establish a connection to jdbc:derby://localhost:1527/sample using
org.apache.derby.jdbc.ClientDriver
(The connection was refused because the database sample was not found.)"

Instead of saying (... because the database sample was not found.)  it would be more useful to suggest the
user to check the Java DB settings in Tools->Java DB Database->Settings... or to make sure another instance
of Derby is not running.

In my case, the Derby settings were correct but I had another installation of Derby running.
Comment 1 John Baker 2007-10-03 23:23:42 UTC 
This is a UI change and probably won't fix for 6.0
Comment 2 John Baker 2007-11-02 09:11:47 UTC 
Created attachment 52336 [details]
diff of fix
Comment 3 John Baker 2007-11-02 09:14:07 UTC 
attached wrong file
Comment 4 Jiri Rechtacek 2009-07-01 07:44:15 UTC 
NB6.7 was released already - http://www.netbeans.org/community/releases/67/
Postpone fixing this issue on the next release.
Comment 5 Jiri Rechtacek 2009-07-01 07:57:31 UTC 
Reassigned to new owner.
Comment 6 Jiri Rechtacek 2009-09-21 13:22:57 UTC 
It's obsolete bug since UI in NB6.5 was changed.