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 143796 - [65cat] java.sql.SQLTransientConnectionException: No current connection.
Summary: [65cat] java.sql.SQLTransientConnectionException: No current connection.
Status: RESOLVED FIXED
Alias: None
Product: db
Classification: Unclassified
Component: SQL Editor (show other bugs)
Version: 6.x
Hardware: All All
: P2 blocker (vote)
Assignee: Andrei Badea
URL: http://statistics.netbeans.org/except...
Keywords:
: 143797 (view as bug list)
Depends on:
Blocks:
 
Reported: 2008-08-13 18:27 UTC by azizi
Modified: 2008-08-15 09:43 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter: 90565

Attachments
stacktrace (1.29 KB, text/plain)
2008-08-13 18:27 UTC, azizi 		Details
stacktrace (1.29 KB, text/plain)
2008-08-13 18:37 UTC, azizi 		Details
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description azizi 2008-08-13 18:27:04 UTC 
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)
Comment 1 azizi 2008-08-13 18:27:21 UTC 
Created attachment 67292 [details]
stacktrace
Comment 2 azizi 2008-08-13 18:37:51 UTC 
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)
Comment 3 azizi 2008-08-13 18:37:54 UTC 
Created attachment 67293 [details]
stacktrace
Comment 4 azizi 2008-08-13 18:44:29 UTC 
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.
Comment 5 Andrei Badea 2008-08-13 20:32:11 UTC 
*** Issue 143797 has been marked as a duplicate of this issue. ***
Comment 6 John Baker 2008-08-14 03:51:53 UTC 
if 143838 is fixed then I think this exception won't occur
Comment 7 Andrei Badea 2008-08-14 10:53:33 UTC 
It won't, but the SQL editor still needs to be fixed to use the test() method.
Comment 8 Andrei Badea 2008-08-15 09:43:17 UTC 
Actually, simplest to modify the code to avoid calling Connection.getMetaData().

#84a0bf5fad8e