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 63881 - Stale connections visible after NetBeans restart
Summary: Stale connections visible after NetBeans restart
Status: RESOLVED INVALID
Alias: None
Product: db
Classification: Unclassified
Component: Derby (show other bugs)
Version: 5.x
Hardware: All All
: P4 blocker (vote)
Assignee: Andrei Badea
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-09-08 12:38 UTC by bakksjo
Modified: 2006-06-19 13:52 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
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 bakksjo 2005-09-08 12:38:19 UTC 
Stopping NetBeans also stops the Derby Server. When NetBeans is restarted, you
can still find in the Runtime tab the same connections that were present before
NetBeans was stopped.

Since it's obvious that these connections no longer work, why are they not
simply cleaned away?
Comment 1 ajacobs3 2006-06-18 03:57:29 UTC 
Right click on the connection.  The options are "Connect",
"Properties", and "Delete".
The Properties window allows you to change the Database URL and User.  This is
very convenient if your database has multiple
schemas and users.
The state of the connection (Closed and Connected) is reflected in
the node.  It's a convenience to have the connection status
graphically displayed.
Users can delete the connection node if they so choose.
I would vote against fixing this "defect" if that were possible.
Comment 2 Andrei Badea 2006-06-19 13:52:10 UTC 
This is not a defect, it is how it is supposed to work. After restart you can
connect the connections (perhpas to another schema, or using another username)
and the Derby server will be started for you.