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 40651 - reading database table data sometimes gives a spurious exception
Summary: reading database table data sometimes gives a spurious exception
Status: RESOLVED WORKSFORME
Alias: None
Product: db
Classification: Unclassified
Component: Code (show other bugs)
Version: 3.x
Hardware: PC Windows ME/2000
: P3 blocker (vote)
Assignee: Radko Najman
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-03-01 15:35 UTC by dynamite
Modified: 2004-03-11 17:17 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
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 dynamite 2004-03-01 15:35:31 UTC 
I am using the latest QA build (25th Feb 2004) and
Oracle 8.1.7. Often, but not always, when reading
a table of data via the 'View data...' menu item,
I get the exception given below. It is fairly
harmless as I actually receive all the data in the
table. It is not clear to me why sometimes I don't
get the exception other than when the exception
seems to occur most often when a query is first run.

*********** Exception occurred ************ at Mon
Mar 01 09:37:08 GMT 2004
java.lang.ArrayIndexOutOfBoundsException: 2 >= 2
	at java.util.Vector.elementAt(Vector.java:432)
	at
javax.swing.table.DefaultTableColumnModel.getColumn(DefaultTableColumnModel.java:280)
	at javax.swing.JTable+2.setSizeAt(JTable.java:2359)
	at javax.swing.JTable+5.setSizeAt(JTable.java:2451)
	at javax.swing.JTable.adjustSizes(JTable.java:2487)
	at javax.swing.JTable.adjustSizes(JTable.java:2455)
	at
javax.swing.JTable.setWidthsFromPreferredWidths(JTable.java:2367)
	at javax.swing.JTable.doLayout(JTable.java:2256)
	at
java.awt.Container.validateTree(Container.java:1470)
	at
java.awt.Container.validateTree(Container.java:1477)
	at
java.awt.Container.validateTree(Container.java:1477)
	at java.awt.Container.validate(Container.java:1445)
	at
javax.swing.RepaintManager.validateInvalidComponents(RepaintManager.java:354)
	at
javax.swing.SystemEventQueueUtilities$ComponentWorkRequest.run(SystemEventQueueUtilities.java:116)
	at
java.awt.event.InvocationEvent.dispatch(InvocationEvent.java:201)
	at
java.awt.EventQueue.dispatchEvent(EventQueue.java:461)
[catch] at
java.awt.EventDispatchThread.pumpOneEventForHierarchy(EventDispatchThread.java:234)
	at
java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:163)
	at
java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:157)
	at
java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:149)
	at
java.awt.EventDispatchThread.run(EventDispatchThread.java:110)
Comment 1 Jiri Skrivanek 2004-03-02 11:48:53 UTC 
I cannot reproduce it. What JDK do you use? What driver? How many
columns, rows does your table have?
Comment 2 dynamite 2004-03-02 15:07:22 UTC 
The JDBC driver is that which comes with Oracle 9.0.1.
JDK version is 1.5.0-beta.

It is also worth pointing out that my activities through NetBeans
included updating tables as well as simply selecting data.

This doesn't seem an easy one to find. I have no reliable steps to
reproduce the problem other than a suspicion that it may be machine
load related.
Comment 3 Jiri Skrivanek 2004-03-03 08:59:25 UTC 
Even with JDK1.5.0 I am not able to reproduce it. Because the
exception doesn't come from NetBeans source code, it is not easy to
track what's wrong. If you find a scenario, how to reproduce, it will
be helpful.
Comment 4 Jiri Skrivanek 2004-03-11 17:17:26 UTC 
Resolving as worksforme. If you are able to reproduce it, feel free to
reopen.