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 196889 - IndexOutOfBoundsException: Index: 0, Size: 0
Summary: IndexOutOfBoundsException: Index: 0, Size: 0
Status: RESOLVED DUPLICATE of bug 216446
Alias: None
Product: connecteddeveloper
Classification: Unclassified
Component: Kenai (show other bugs)
Version: 6.x
Hardware: All All
: P3 normal (vote)
Assignee: Tomas Stupka
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-03-20 12:54 UTC by Exceptions Reporter
Modified: 2012-12-06 11:30 UTC (History)
2 users (show)

See Also:
Issue Type: DEFECT
Exception Reporter: 160416


Attachments
stacktrace (1.18 KB, text/plain)
2011-03-20 12:54 UTC, Exceptions Reporter
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Exceptions Reporter 2011-03-20 12:54:33 UTC
Build: NetBeans IDE 6.9.1 (Build 201011082200)
VM: Java HotSpot(TM) Client VM, 19.0-b09, Java(TM) SE Runtime Environment, 1.6.0_23-b05
OS: Windows Vista

User Comments:
GUEST: IDE Starting

soldatov: push my changes on kenai.com

GUEST: I have deleted var/cache before starting NetBeans, then saw this exception.

GUEST: Starting NetBeans.

soldatov: push source files on kenai.com

yardus: Recieving a message in the minimized chat wndow




Stacktrace: 
java.lang.IndexOutOfBoundsException: Index: 0, Size: 0
   at java.util.ArrayList.RangeCheck(ArrayList.java:547)
   at java.util.ArrayList.get(ArrayList.java:322)
   at java.util.Collections$UnmodifiableList.get(Collections.java:1154)
   at org.netbeans.modules.kenai.collab.chat.ChatPanel.getMessageBody(ChatPanel.java:1073)
   at org.netbeans.modules.kenai.collab.chat.ChatPanel.insertMessage(ChatPanel.java:1087)
   at org.netbeans.modules.kenai.collab.chat.ChatPanel$ChatListener$1.run(ChatPanel.java:621)
Comment 1 Exceptions Reporter 2011-03-20 12:54:37 UTC
Created attachment 107132 [details]
stacktrace
Comment 2 Ondrej Vrabec 2012-12-06 11:30:41 UTC

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