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.
Found in nb42dev build 200508161800 1. start nb 2. add sun app server 3. add web logic 9 4. add new db connection for web logic pointbase => everytime you want to use this connection the sun app server pointbase tries to connect and due to i am not able to use any other pointbase without the error messages from sjsas pointbase.
The Tools->Pointbase->Start Local... item starts the server associated with the SJSAS instance. (It is registered by the sjsas plugin) It seems like the Databases->connection instance node is using some hook that knows how to start an instance. It may be using stuff that it should not... I will dig in a bit more...
The connection's Connect... ends up calling RegisterPointbase.start() This is due to the fact that RegisterPointbase implements DatabaseRuntime. This is a great idea, but doesn't scale as this issue shows.
Some background first, just to be sure: each server which bundles a database can implement the DatabaseRuntime interface, which allows the server to start the database when a connection is made to it. Upon connecting, the following methods are called on DatabaseRuntime: - isStarted() - if it returns true, this DR is ignored - canStart() - if it returns false, this DR is ignored - acceptsConnectionUrl() - if it returns false, this DR is ignored RegisterPointbase returns true from acceptsConnectionUrl() when the url parameter starts with "jdbc:pointbase", which is obviously incorrect. It should compare the url parameter to its DATABASE_URL and DATABASE_URL2 fields. Please note that the acceptsConnectionUrl() method will be renamed to the more correct acceptsDatabaseURL soon.
Just realized that comparing to the DATABASE_URL fields is not correct either. If you create another database, the server won't be started for it. So probably you should only test the host and port, i.e, jdbc:pointbase://localhost:9092.
What host/port does the weblogic install use for their pointbase install?
wl pointbase uses same options like sjsas's pointbase localhost:9092
In an e-mail conversation with Vince he suggests adding a method for retrieving the JDBCDriver instance to DatabaseConnection and passing a DatabaseConnection instance to DatabaseRuntime.acceptsDatabaseURL(). Then it would be possible to decide whether to start the server based on the JDBCDriver URLs. While the latter is doable, the former is not, since DatabaseConnection doesn't maintain a JDBCDriver instance (it only has properties for the driver class and name). Since WebLogic uses the same host and port as appserver, we could to check the database name in the implementation of DR.acceptsDatabaseURL(). To reporter: could you get a list of the databases in the WebLogic's Pointbase?
Please note that the correct fix of this issue depends on issue 65426, which is an incompatible API change. Because of this and because the required API change is not the nicest one I want to drive issue 65426 through an API review. If the API review is denied because we're after feature freeze, this issue will be either not be fixed in 5.0, or it will have to be fixed in another way (for example the one I suggested in my comment from Sep 26).
The 26 Sep 2005 suggestion isn't very bullet-proof. I have another work-around that may be better, but even that isn't bullet-proof. Basically, most of the "fixes" that I can figure out will be trading a P3 bug for a P3 bug...
http://serverplugins.netbeans.org/servlets/ReadMsg?list=cvs&msgNo=960
NOTE: This fix ONLY addresses new instance registrations. Existing registered instances may still exhibit this issue.
Vince, if you want, I could add some code to the Database Explorer to set database.home to Poinbase connections. True, it would be a bit of a hack. But the question is what to set it to. Should I try to do System.getProperty("com.sun.aas.installRoot") and if returns a non-null value, set database.home to something based on it?
rollbacked
TM 5.0->TBD
p4: pointbase is not the key feature going forward... Only old 8.1 users might see this.
This was marked as fix-in-50, I am changing to fix-in-55, but is this still important? Pointbase is now deprecated.
ludo lowered the priority to p4. I would infer that he does not think this is a critical issue.
Ok, removing fix-in-55; QE, please speak up if you disagree.
I need to play with this again... probably in the 7.0 time frame. Pushing back up to p3.. to get it back 'on the radar'.
not enough need to justify possible stop-ship
No supported servers ship with pointbase, so this is fixed by changes in the servers and the support matrix.