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 178074 - org.apache.derby.client.am.SqlException: No current connection.
Summary: org.apache.derby.client.am.SqlException: No current connection.
Status: RESOLVED WORKSFORME
Alias: None
Product: db
Classification: Unclassified
Component: Code (show other bugs)
Version: 6.x
Hardware: All All
: P3 normal (vote)
Assignee: Jiri Rechtacek
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-12-03 06:07 UTC by Alexander Permyakov
Modified: 2011-01-27 07:55 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
Exception Reporter: 163286

Attachments
stacktrace (3.42 KB, text/plain)
2009-12-03 06:07 UTC, Alexander Permyakov 		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 Alexander Permyakov 2009-12-03 06:07:17 UTC 
Build: NetBeans IDE 6.7.1 (Build 200907230101)
VM: Java HotSpot(TM) Client VM, 11.0-b16, Java(TM) SE Runtime Environment, 1.6.0_11-b03
OS: Windows XP, 5.1, x86

User Comments:
alex02: try to connect and refresh connection for derby DataBase



Stacktrace: 
org.apache.derby.client.am.SqlException: No current connection.
        at org.apache.derby.client.am.Connection.checkForClosedConnection(Connection.java:0)
        at org.apache.derby.client.am.Connection.getCatalog(Connection.java:0)
        at org.netbeans.modules.db.metadata.model.jdbc.JDBCMetadata.createCatalogs(JDBCMetadata.java:141)
        at org.netbeans.modules.db.metadata.model.jdbc.JDBCMetadata.initCatalogs(JDBCMetadata.java:183)
        at org.netbeans.modules.db.metadata.model.jdbc.JDBCMetadata.getCatalog(JDBCMetadata.java:107)
        at org.netbeans.modules.db.metadata.model.api.Metadata.getCatalog(Metadata.java:108)
Comment 1 Alexander Permyakov 2009-12-03 06:07:20 UTC 
Created attachment 92049 [details]
stacktrace
Comment 2 Jiri Rechtacek 2011-01-27 07:55:32 UTC 
We are trying to prioritize bugs but do not have time to evaluate all open P3s, please reopen if you feel this bug is still valid.