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 174969 - NullPointerException at java.util.Hashtable.put
Summary: NullPointerException at java.util.Hashtable.put
Status: RESOLVED INVALID
Alias: None
Product: db
Classification: Unclassified
Component: Code (show other bugs)
Version: 6.x
Hardware: All All
: P4 blocker (vote)
Assignee: Jiri Rechtacek
URL: http://statistics.netbeans.org/except...
Keywords:
Depends on:
Blocks:
 
Reported: 2009-10-20 10:07 UTC by aprknight
Modified: 2012-09-30 13:54 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter: 95879

Attachments
stacktrace (7.66 KB, text/plain)
2009-10-20 10:07 UTC, aprknight 		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 aprknight 2009-10-20 10:07:19 UTC 
Build: NetBeans IDE 6.5.1 (Build 200905151554)
VM: Java HotSpot(TM) 64-Bit Server VM, 14.1-b02-90, Java(TM) SE Runtime Environment, 1.6.0_15-b03-219
OS: Mac OS X, 10.6.1, x86_64

Stacktrace: 
java.lang.NullPointerException
        at java.util.Hashtable.put(Hashtable.java:394)
        at org.axiondb.engine.tables.RSSTable.getTableProperties(RSSTable.java:327)
        at org.axiondb.engine.metaupdaters.AxionTablePropertiesMetaTableUpdater.createRowsForAddedTable(AxionTablePropertiesMetaTableUpdater.java:115)
        at org.axiondb.engine.metaupdaters.AxionTablePropertiesMetaTableUpdater.tableAdded(AxionTablePropertiesMetaTableUpdater.java:92)
        at org.axiondb.engine.BaseDatabase.addTable(BaseDatabase.java:189)
        at org.axiondb.engine.DiskDatabase.loadTables(DiskDatabase.java:431)
Comment 1 aprknight 2009-10-20 10:07:25 UTC 
Created attachment 89746 [details]
stacktrace
Comment 2 Jiri Rechtacek 2009-10-20 18:43:21 UTC 
Not supported JDBC driver => changing the priority.
Comment 3 matthias42 2012-09-30 13:54:48 UTC 
The last time this happend was two years ago - the error as far as the stacktrace can give that information lies in the driver itself.