Exception in thread "AWT-EventQueue-0" ArrayIndexOutofBoundsException:

My app keeps throwing this error:

Exception in thread "AWT-EventQueue-0" java.lang.ArrayIndexOutOfBoundsException: No such child: 0

at java.awt.Container.getComponent(Unknown Source)

at javax.swing.JComponent.rectangleIsObscured(Unknown Source)

at javax.swing.JComponent.paint(Unknown Source)

at javax.swing.JComponent.paintToOffscreen(Unknown Source)

at javax.swing.BufferStrategyPaintManager.paint(Unknown Source)

at javax.swing.RepaintManager.paint(Unknown Source)

at javax.swing.JComponent._paintImmediately(Unknown Source)

at javax.swing.JComponent.paintImmediately(Unknown Source)

at javax.swing.RepaintManager.paintDirtyRegions(Unknown Source)

at javax.swing.RepaintManager.paintDirtyRegions(Unknown Source)

at javax.swing.RepaintManager.seqPaintDirtyRegions(Unknown Source)

at javax.swing.SystemEventQueueUtilities$ComponentWorkRequest.run(Unknown Source)

at java.awt.event.InvocationEvent.dispatch(Unknown Source)

at java.awt.EventQueue.dispatchEvent(Unknown Source)

at java.awt.EventDispatchThread.pumpOneEventForFilters(Unknown Source)

at java.awt.EventDispatchThread.pumpEventsForFilter(Unknown Source)

at java.awt.EventDispatchThread.pumpEventsForHierarchy(Unknown Source)

at java.awt.EventDispatchThread.pumpEvents(Unknown Source)

at java.awt.EventDispatchThread.pumpEvents(Unknown Source)

at java.awt.EventDispatchThread.run(Unknown Source)

I am using Eclipse 3.1. How do I know what line this is getting triggered on?

[1572 byte] By [grozniy_99a] at [2007-11-27 6:02:51]
# 1

> How do I know what line this is getting triggered on?

by trace your exception message:

at java.awt.Container.getComponent(Unknown Source)

at javax.swing.JComponent.rectangleIsObscured(Unknown Source)

at javax.swing.JComponent.paint(Unknown Source)

at javax.swing.JComponent.paintToOffscreen(Unknown Source)

at javax.swing.BufferStrategyPaintManager.paint(Unknown Source)

at javax.swing.RepaintManager.paint(Unknown Source)

at javax.swing.JComponent._paintImmediately(Unknown Source)

at javax.swing.JComponent.paintImmediately(Unknown Source)

at javax.swing.RepaintManager.paintDirtyRegions(Unknown Source)

at javax.swing.RepaintManager.paintDirtyRegions(Unknown Source)

at javax.swing.RepaintManager.seqPaintDirtyRegions(Unknown Source)

at javax.swing.SystemEventQueueUtilities$ComponentWorkRequest.run(Unknown Source)

at java.awt.event.InvocationEvent.dispatch(Unknown Source)

at java.awt.EventQueue.dispatchEvent(Unknown Source)

at java.awt.EventDispatchThread.pumpOneEventForFilters(Unknown Source)

at java.awt.EventDispatchThread.pumpEventsForFilter(Unknown Source)

at java.awt.EventDispatchThread.pumpEventsForHierarchy(Unknown Source)

at java.awt.EventDispatchThread.pumpEvents(Unknown Source)

at java.awt.EventDispatchThread.pumpEvents(Unknown Source)

at java.awt.EventDispatchThread.run(Unknown Source)

maybe you try to call someContainer.getComponent(i) which someContainer does not has any child component.

j_shadinataa at 2007-7-12 16:44:42 > top of Java-index,Java Essentials,New To Java...
# 2
I don't know where the trace the exception. I don't know what line it's caused by. Any ideas on how to make Eclipse tell me that?
grozniya at 2007-7-12 16:44:42 > top of Java-index,Java Essentials,New To Java...
# 3
> I don't know where the trace the exception. I don't> know what line it's caused by. Any ideas on how to> make Eclipse tell me that?Was that the full stacktrace?
kajbja at 2007-7-12 16:44:42 > top of Java-index,Java Essentials,New To Java...
# 4
that's all I see
grozniy_99a at 2007-7-12 16:44:42 > top of Java-index,Java Essentials,New To Java...
# 5
That's all eclipse shows for the errors.
grozniy_99a at 2007-7-12 16:44:42 > top of Java-index,Java Essentials,New To Java...
# 6
There is some problem with the way you have set up your GUI components. It's not possible to say more by looking at the stack trace only.
jsalonena at 2007-7-12 16:44:42 > top of Java-index,Java Essentials,New To Java...
# 7

If you're really not sure and using eclipse, you can always insert a break point some place before you *think* the Exception is occurring, and then just continually step into the program until you find it via debugging.

edit: Or insert System.out.println() messages in your program so you have an idea of around where it's happening.

Message was edited by:

JJCoolB

JJCoolBa at 2007-7-12 16:44:42 > top of Java-index,Java Essentials,New To Java...