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.
Using the NetBeans DB tooling with SAP MaxDB, at the moment I am not able to work with the connections anymore. Behaviour: - Connecting to / disconnecting from the DB causes an exception to be thrown: http://statistics.netbeans.org/analytics/detail.do?id=67517 - By then, when connected, browsing database views and tables works fine but when doing "execute SQL", the database source is not pre-selected, and selecting it also doesn't cause a command to be executed. - The IDE log file provides an exception dump not reported by the IDE, see below. State: The DB Tooling is unusable with MaxDB due to that. Versions: Product Version: NetBeans IDE Dev (Build 200806190009) Java: 1.6.0_10-beta; Java HotSpot(TM) Client VM 11.0-b11 System: Linux version 2.6.24-19-generic running on i386; UTF-8; de_DE (nb) Userdir: /home/kr/.netbeans/dev-6.1 SAP MaxDB 7.6.00.00.3360 JDBC Driver Exception: SEVERE [global] com.sap.dbtech.jdbc.exceptions.ObjectIsClosedException: SAP DBTech JDBC: Object is closed. at com.sap.dbtech.jdbc.ResultSetSapDB.assertNotClosed(ResultSetSapDB.java:2706) at com.sap.dbtech.jdbc.ResultSetSapDB.getMetaData(ResultSetSapDB.java:1100) at org.netbeans.lib.ddl.impl.DriverSpecification.getRow(DriverSpecification.java:225) at org.netbeans.modules.db.explorer.infos.TableListNodeInfo.initChildren(TableListNodeInfo.java:96) Caused: org.netbeans.api.db.explorer.DatabaseException: SAP DBTech JDBC: Object is closed. at org.netbeans.modules.db.explorer.infos.TableListNodeInfo.initChildren(TableListNodeInfo.java:110) at org.netbeans.modules.db.explorer.infos.DatabaseNodeInfo.getChildren(DatabaseNodeInfo.java:687) at org.netbeans.modules.db.explorer.infos.DatabaseNodeInfo.refreshChildren(DatabaseNodeInfo.java:351) at org.netbeans.modules.db.explorer.infos.ConnectionNodeInfo.refreshChildren(ConnectionNodeInfo.java:498) at org.netbeans.modules.db.explorer.infos.ConnectionNodeInfo.update(ConnectionNodeInfo.java:195) at org.netbeans.modules.db.explorer.infos.ConnectionNodeInfo.access$000(ConnectionNodeInfo.java:74) [catch] at org.netbeans.modules.db.explorer.infos.ConnectionNodeInfo$1.propertyChange(ConnectionNodeInfo.java:92) at java.beans.PropertyChangeSupport.firePropertyChange(PropertyChangeSupport.java:339) at java.beans.PropertyChangeSupport.firePropertyChange(PropertyChangeSupport.java:276) at org.netbeans.modules.db.explorer.infos.DatabaseNodeInfo.setConnection(DatabaseNodeInfo.java:491) at org.netbeans.modules.db.explorer.infos.ConnectionNodeInfo.finishConnect(ConnectionNodeInfo.java:427) at org.netbeans.modules.db.explorer.infos.ConnectionNodeInfo.connect(ConnectionNodeInfo.java:347) at org.netbeans.modules.db.explorer.infos.ConnectionNodeInfo.finishConnect(ConnectionNodeInfo.java:430) at org.netbeans.modules.db.explorer.actions.ConnectAction$ConnectionDialogDisplayer$3.propertyChange(ConnectAction.java:230) at java.beans.PropertyChangeSupport.firePropertyChange(PropertyChangeSupport.java:339) at java.beans.PropertyChangeSupport.firePropertyChange(PropertyChangeSupport.java:276) at org.netbeans.modules.db.explorer.DatabaseConnection$2.run(DatabaseConnection.java:543) at org.openide.util.RequestProcessor$Task.run(RequestProcessor.java:561) at org.openide.util.RequestProcessor$Processor.run(RequestProcessor.java:986)
Hi, it appears you're using a nightly build ? Could you successfully connect to MaxDB and execute queries in previous NetBeans releases?
yes it worked smoothly in 6.1 AFAIR. noticed this to be broken for the first time more or less two weeks ago (usually updating to the latest nightly build for testing purposes every morning), but didn't need it so far.
Nightly builds can be very unstable. If this worked in 6.1 then I would recommend to stick with 6.1 Otherwise, in the meantime, as a last resort (you'll lose your settings unless you back up your userdir), you could delete your userdir to see if this helps.
I will give it a try; nevertheless I thought using and testing nightly builds in order to find issues is the very idea of nightly builds after all? ;)
I agree, testing with nightly builds is a very good thing and thanks for reporting this issue. SAPDB/MaxDB is not one of our supported databases (there are just stacks of them out there and we are not able to handle them all). So we will definitely look at this, but it can't be a P1 (which means it blocks the release). the stack trace thrown looks familiar, someone else saw this when their memory allocated to NetBeans was way to small. Is your memory allocation correct? See http://wiki.netbeans.org/FaqMemoryReqs and http://wiki.netbeans.org/FaqSettingHeapSize. But I suspect you're fine, since you've been running with 6.1 just fine. It looks like the original cause is the stack trace, which I suspect is disconnecting the database, and then you can't do anything because the connection is closed ("Object is closed"). Downgrading this to a P2 - now we need to get a MaxDB environment set up... :)
Issue 137811 is the same stack trace that you reported
Trying to track this down - were you connecting/disconnecting or were you actually *removing* the connection and creating a new one?
By the way, did you try to delete your userdir and start again?
Never mind, I found the root cause (issue 137811), and cleaning out the userdir will *not* help. I'd still like to know exactly what you're doing. I suspect you're changing a property on the connection and then trying to remove the connection. Can you tell me the exact steps, it would be much appreciated.
I am closing as a duplicate as I believe 137811 is the root cause of your problem. If you still have issues, please definitely re-open. *** This issue has been marked as a duplicate of 137811 ***
I think it is fixed now, at least the behaviour is not there anymore in recent builds so I'm marking this as verified.