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 268434 - NullPointerException at com.ddtek.jdbc.openedgebase.BaseDatabaseMetaData.supportsSchemasInTableDefinitions
Summary: NullPointerException at com.ddtek.jdbc.openedgebase.BaseDatabaseMetaData.supp...
Status: RESOLVED DUPLICATE of bug 166367
Alias: None
Product: db
Classification: Unclassified
Component: Code (show other bugs)
Version: Dev
Hardware: All All
: P3 normal (vote)
Assignee: matthias42
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-10-09 23:28 UTC by brettryan
Modified: 2016-11-04 21:16 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter: 226659


Attachments
stacktrace (3.35 KB, text/plain)
2016-10-09 23:28 UTC, brettryan
Details

Note You need to log in before you can comment on or make changes to this bug.
Description brettryan 2016-10-09 23:28:41 UTC
Build: NetBeans IDE Dev (Build 201610020002)
VM: Java HotSpot(TM) 64-Bit Server VM, 25.102-b14, Java(TM) SE Runtime Environment, 1.8.0_102-b14
OS: Mac OS X

User Comments:
brettryan: SQL driver network error (broken pipe).




Stacktrace: 
java.lang.NullPointerException
   at com.ddtek.jdbc.openedgebase.BaseDatabaseMetaData.supportsSchemasInTableDefinitions(BaseDatabaseMetaData.java:0)
   at org.netbeans.modules.db.metadata.model.jdbc.JDBCCatalog.createSchemas(JDBCCatalog.java:134)
   at org.netbeans.modules.db.metadata.model.jdbc.JDBCCatalog.initSchemas(JDBCCatalog.java:190)
   at org.netbeans.modules.db.metadata.model.jdbc.JDBCCatalog.getSyntheticSchema(JDBCCatalog.java:98)
   at org.netbeans.modules.db.metadata.model.api.Catalog.getSyntheticSchema(Catalog.java:94)
   at org.netbeans.modules.db.explorer.node.SchemaNodeProvider$1.run(SchemaNodeProvider.java:119)
Comment 1 brettryan 2016-10-09 23:28:43 UTC
Created attachment 162421 [details]
stacktrace
Comment 2 matthias42 2016-10-10 17:29:33 UTC
This is a driver bug. DatabaseMetaData#supportsSchemasInTableDefinitions is defined as throwing an SQLException " if a database access error occurs" (quote from doc). So there is no reason to accept a NullPointerException.

I'll look into catching RuntimeException there, but this should be raised with the DB driver vendor.
Comment 3 matthias42 2016-11-04 21:16:59 UTC

*** This bug has been marked as a duplicate of bug 166367 ***