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.
| Summary: | Database started from ant/command line does not shown at Tool>Java DB Database | ||
|---|---|---|---|
| Product: | db | Reporter: | davisn <davisn> |
| Component: | Derby | Assignee: | Libor Fischmeistr <lfischmeistr> |
| Status: | NEW --- | ||
| Severity: | blocker | CC: | issues |
| Priority: | P3 | ||
| Version: | 5.x | ||
| Hardware: | All | ||
| OS: | All | ||
| Issue Type: | ENHANCEMENT | Exception Reporter: | |
| Bug Depends on: | |||
| Bug Blocks: | 152818 | ||
-> db/derby 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? this node is owned by the db team now Reassigned to new owner. |
If a database is started at a command line, the started status will not shown at the Tool > Java DB Database menu STEPS TO REPRODUCE: 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 asadmin>start-database 5. From IDE, select Runtime > Database > jdbc:derby://localhost:1527/sun-apps... right-click to select Connect Note: You should be able to connect to the database 6. Select Tool > Java DB Database menu BUG: It was not shown that sun-appserver-sample database was already started