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 262220 - java.sql.SQLException: no database metadata available
Summary: java.sql.SQLException: no database metadata available
Status: RESOLVED FIXED
Alias: None
Product: db
Classification: Unclassified
Component: Code (show other bugs)
Version: 8.0
Hardware: All All
: P3 normal (vote)
Assignee: matthias42
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-05-25 12:52 UTC by Exceptions Reporter
Modified: 2016-05-28 23:06 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter: 224205

Attachments
stacktrace (590 bytes, text/plain)
2016-05-25 12:52 UTC, Exceptions Reporter 		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 Exceptions Reporter 2016-05-25 12:52:07 UTC 
This bug was originally marked as duplicate of bug 206835, that is already resolved. This bug is still valid, so this seems to be another bug, but it might be related.

Build: NetBeans IDE 8.0.2 (Build 201411181905)
VM: Java HotSpot(TM) 64-Bit Server VM, 25.40-b25, Java(TM) SE Runtime Environment, 1.8.0_40-b26
OS: Windows 8

User Comments:
GUEST: Running SQL Query




Stacktrace: 
java.sql.SQLException: no database metadata available
   at org.netbeans.lib.ddl.adaptors.DefaultAdaptor.isReadOnly(DefaultAdaptor.java:438)
   at org.netbeans.modules.db.explorer.node.ConnectionNode.updateLocalProperties(ConnectionNode.java:224)
   at org.netbeans.modules.db.explorer.node.ConnectionNode.access$300(ConnectionNode.java:84)
   at org.netbeans.modules.db.explorer.node.ConnectionNode$2.run(ConnectionNode.java:362)
   at org.openide.util.RequestProcessor$Task.run(RequestProcessor.java:1423)
   at org.openide.util.RequestProcessor$Processor.run(RequestProcessor.java:2033)
Comment 1 Exceptions Reporter 2016-05-25 12:52:09 UTC 
Created attachment 159871 [details]
stacktrace
Comment 2 matthias42 2016-05-28 23:06:26 UTC 
The fix was committed as:

http://hg.netbeans.org/core-main/rev/b35cfca2d60c

This problem originates in the updating of the connection node properties. If an exception happend there, it was always reported on the SEVERE level. The severance was reduced to the INFO level, that puts the message into the log and if this masked a real bug, that bug should be reported.