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 140538 - org.netbeans.api.db.explorer.DatabaseException: Cursor position not valid.
Summary: org.netbeans.api.db.explorer.DatabaseException: Cursor position not valid.
Status: RESOLVED WONTFIX
Alias: None
Product: db
Classification: Unclassified
Component: Code (show other bugs)
Version: 6.x
Hardware: All All
: P3 blocker (vote)
Assignee: David Vancouvering
URL: http://statistics.netbeans.org/except...
Keywords:
Depends on:
Blocks:
 
Reported: 2008-07-17 14:47 UTC by gholmer
Modified: 2008-07-29 20:44 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
Exception Reporter: 77856

Attachments
stacktrace (125 bytes, text/plain)
2008-07-17 14:47 UTC, gholmer 		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 gholmer 2008-07-17 14:47:32 UTC 
Build: NetBeans IDE Dev (Build 200807170007)
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: 
I have a database connection to an AS/400 (IBM iSeries). I opened it to tables view, then right-clicked the "Tables" node and selected Refresh.
Comment 1 gholmer 2008-07-17 14:47:36 UTC 
Created attachment 64854 [details]
stacktrace
Comment 2 David Vancouvering 2008-07-29 18:57:52 UTC 
Does this happen every time or did it only happen once?
Comment 3 gholmer 2008-07-29 19:12:04 UTC 
Just tried it again with the 0729 build and it still happens and is repeatable.  Doesn't happen with a Postgres table.
Comment 4 David Vancouvering 2008-07-29 20:44:44 UTC 
I have no access to an AS/400 and the AS/400 is not a supported database.  I suspect that the JDBC driver for the AS/400
does not correctly support delivering database metadata.

If you give me the full stack trace, I can potentially tell you how to write a JDBC application that reproduces the
problem and then you can take this to IBM support so they can fix it, but beyond that there's not much I can do.

You might also try upgrading the driver, if you don't have the latest driver.