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 80774 - Database started from ant/command line does not shown at Tool>Java DB Database
Summary: Database started from ant/command line does not shown at Tool>Java DB Database
Status: NEW
Alias: None
Product: db
Classification: Unclassified
Component: Derby (show other bugs)
Version: 5.x
Hardware: All All
: P3 blocker (vote)
Assignee: Libor Fischmeistr
Depends on:
Blocks: 152818
  Show dependency tree
Reported: 2006-07-21 02:56 UTC by davisn
Modified: 2013-08-01 12:53 UTC (History)
1 user (show)

See Also:
Exception Reporter:


Note You need to log in before you can comment on or make changes to this bug.
Description davisn 2006-07-21 02:56:35 UTC
If a database is started at a command line, the started status will not shown at
the Tool > Java DB Database menu

1. Install AppServer 9PE SDK version
2. Install Netbean IDE 5.5 - build 7/20
3. Expand IDE > Runtime > Database, select New Connection and add\
    Database URL: jdbc:derby://localhost:1527/sun-appserv-samples;create=true
    User Name: APP
    Password: APP
4. Go to ../AppServer/bin and execute
5. From IDE, select Runtime > Database > jdbc:derby://localhost:1527/sun-apps...
    right-click to select Connect
   You should be able to connect to the database
6. Select Tool > Java DB Database menu
    It was not shown that sun-appserver-sample database was already started
Comment 1 Sherold Dev 2006-07-21 09:37:31 UTC
-> db/derby
Comment 2 Andrei Badea 2006-07-28 13:15:14 UTC
This is not a defect, not detecting that the server database is running is by
intention. At least enabling the Stop Java DB Server action is not trivial,
since we have to know how the database was started in order to know how to stop
it. It could have been started e.g. by the user manually by running the
startNetworkServer.ksh script.

OTOH is the appserver plugin could tell that the server was started by the
asadmin tool we would be probably able to stop it (or the plugin could do it).
Ludo, is this possible?
Comment 3 Vince Kraemer 2009-09-25 21:18:09 UTC
this node is owned by the db team now
Comment 4 Jiri Rechtacek 2009-10-16 14:08:50 UTC
Reassigned to new owner.