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.
Build: NetBeans IDE Dev (Build 200808061401) VM: Java HotSpot(TM) Client VM, 10.0-b22, Java(TM) SE Runtime Environment, 1.6.0_06-b02 OS: Linux, 2.6.24-19-generic, i386 User Comments: Stacktrace: java.sql.SQLTransientConnectionException: No current connection. at org.apache.derby.client.am.SQLExceptionFactory40.getSQLException(SQLExceptionFactory40.java:0) at org.apache.derby.client.am.SqlException.getSQLException(SqlException.java:0) at org.apache.derby.client.am.Connection.getMetaData(Connection.java:0) at org.netbeans.modules.db.sql.execute.SQLExecuteHelper.execute(SQLExecuteHelper.java:90) at org.netbeans.modules.db.sql.loader.SQLEditorSupport$SQLExecutor.run(SQLEditorSupport.java:480) at org.openide.util.RequestProcessor$Task.run(RequestProcessor.java:572)
Created attachment 67292 [details] stacktrace
Created attachment 67293 [details] stacktrace
1.start IDE. 2.start Java DB server from services tab. 3.right click on one of jdbc:derby connections and select connect from menu. 4.right click on one table and select view data. 5.stop java DB server 6.from sql command tab click onrun sql button 7.a message appear that connection is lost 8.again click on run sql button 9. exception occur I'm able to reproduce it again and again.
*** Issue 143797 has been marked as a duplicate of this issue. ***
if 143838 is fixed then I think this exception won't occur
It won't, but the SQL editor still needs to be fixed to use the test() method.
Actually, simplest to modify the code to avoid calling Connection.getMetaData(). #84a0bf5fad8e