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 262845 - [82cat] Alterations to Derby Database Location should invalidate existing derby connections
Summary: [82cat] Alterations to Derby Database Location should invalidate existing der...
Status: NEW
Alias: None
Product: db
Classification: Unclassified
Component: Derby (show other bugs)
Version: 8.2
Hardware: All All
: P4 normal (vote)
Assignee: Libor Fischmeistr
Depends on:
Reported: 2016-07-18 05:43 UTC by brettryan
Modified: 2016-07-18 05:43 UTC (History)
0 users

See Also:
Exception Reporter:


Note You need to log in before you can comment on or make changes to this bug.
Description brettryan 2016-07-18 05:43:47 UTC
If the derby location is altered it is advised that any existing derby connections be invalidated to ensure that they exist in the new database location.

Steps to Reproduce
1. Open Services (Cmd+5)
2. With a fresh installation the default `sample` database connection should be available.
3. Right click `Java DB` and choose `Properties...`
4. Alter the location of `Database Location` to a new path, say by appending `2`.
5. Click `OK`.
6. Try to connect to the sample database `jdbc:derby://localhost:1527/sample [app on APP]`.

Expected Result
All existing derby connections should be removed and new ones added for any database that has been found within the new database location folder if it already existed.

Only localhost:1527 connections should be considered for removal.

Actual Result
No database connections are removed or added, thus trying to connect to the sample produces the error `Unable to Connect...`.