Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 361654 - ArrayIndexOutOfBoundsException prevent starting (resolving) a cquery or open the component explorer
Summary: ArrayIndexOutOfBoundsException prevent starting (resolving) a cquery or open ...
Status: RESOLVED NOT_ECLIPSE
Alias: None
Product: z_Archived
Classification: Eclipse Foundation
Component: Buckminster (show other bugs)
Version: unspecified   Edit
Hardware: PC Linux
: P3 critical (vote)
Target Milestone: ---   Edit
Assignee: buckminster.core-inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-10-21 09:58 EDT by Thomas Pohl CLA
Modified: 2019-02-25 14:41 EST (History)
1 user (show)

See Also:

Attachments
stacktraces (5.27 KB, text/plain)
2011-10-21 09:59 EDT, Thomas Pohl CLA 		no flags Details
View All 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 Thomas Pohl CLA 2011-10-21 09:58:15 EDT 
Build Identifier: M20110909-1335

No matter what kind of a cquery I try to start I get the following exception:
java.lang.ArrayIndexOutOfBoundsException: Array index out of range: 118

The same happens if I open the component explorer or when using -> window -> preferences -> Buckminster -> Refresh Meta Data.



Reproducible: Always

Steps to Reproduce:
1. open any cquery and click on resolve
or
1. open the component explorer
Comment 1 Thomas Pohl CLA 2011-10-21 09:59:32 EDT 
Created attachment 205722 [details]
stacktraces
Comment 2 Thomas Hallgren CLA 2011-10-21 10:29:29 EDT 
The enumeration returned by the java.util.Properties should never throw an ArrayIndexOutOfBounds exception so something must be wrong in the implementation.

The stack trace for the Properties class is not applicable to the runtime libraries provided with OpenJDK or an Oracle JVM so I cannot really determine the cause. 

I suggest you try this with OpenJDK. If the problem persist, then feel free to post the stack-trace here and I'll investigate further. For now, I have to assume that this is a bug in J9.
Comment 3 Thomas Pohl CLA 2011-10-21 10:46:21 EDT 
I tried to recreate the issue with OpenJDK and your assumptions were right! Everything worked fine, so I'll try to address this issue to the J9 development. Thank you very much for the clarification!