: BUG java.lang.ArrayIndexOutOfBoundsException: 128
"George T. Joseph" wrote:
> Jeez, you're making me sorry I even spoke up. I set the test
> code to end at 128 because that is what YOU guys do in
> DeferredDocumentImpl.
I'm sorry if I gave you that impression. I'
"George T. Joseph" wrote:
> Jeez, you're making me sorry I even spoke up. I set the test
> code to end at 128 because that is what YOU guys do in
> DeferredDocumentImpl.
I'm sorry if I gave you that impression. I'm extremely busy
at the moment and just quickly checked to make sure that the
bi
ust before "int value = values[middle];" (where the exception
is thrown) and run it through DOMCount.
-Original Message-
From: Andy Clark [mailto:[EMAIL PROTECTED]
Sent: Thursday, February 03, 2000 7:23 PM
To: [EMAIL PROTECTED]
Subject: Re: BUG java.lang.ArrayIndexOutOfBoundsE
"George T. Joseph" wrote:
> int[] n = new int[128];
> for(int i=0;i int rc = DeferredDocumentImpl.binarySearch(n, 0, 128,
> Integer.parseInt(argv[0]));
> System.out.println("Index: "+rc);
The start and end points passed into the binarySearch method
are INCLUSIVE. Therefore, you are causin
argv)
{
int[] n = new int[128];
for(int i=0;imailto:[EMAIL PROTECTED]
Sent: Thursday, February 03, 2000 2:48 PM
To: [EMAIL PROTECTED]
Subject: Re: BUG java.lang.ArrayIndexOutOfBoundsException: 128
"George T. Joseph" wrote:
>
> Don't be so quick to blame HotSpot here!! This f
"George T. Joseph" wrote:
>
> Don't be so quick to blame HotSpot here!! This fails with Karen's files on
> Sun
> win32 1.2.2 both classic and HotSpot and also on IBM Win32 1.1.8.
We've had a lot of problem with HotSpot causing people to report
false bugs. HotSpot *does* have problems because mo
where start=end=middle=128 and that's not a valid index in a array of
128 elements.
Either call binarySearch with fIdCount-1 or change start<=end to startmailto:[EMAIL PROTECTED]
Sent: Wednesday, February 02, 2000 4:53 PM
To: [EMAIL PROTECTED]
Subject: Re: BUG java.lang.ArrayIndexOutOfBou
You should dump Hotspot. It has problems running correct Java class
files, that
other VM's (Sun Classic JVM, IBM JVM, etc.) have no trouble running.
At least, that is our experience with Hotspot.
Mike
Karen Schuchardt wrote:
>
> This is in reference to a previous mail under the same subject.
This is in reference to a previous mail under the same subject. Please
refer to it for the full
example.
I am using the vanilla Java 1.2 version (not 1.2.x) and xerces 1.0.1
under Solaris 2.6.
Should I be upgrading to a newer version of java?
Thanks,
karen
Let me take a wild guess... Yo
Sorry if you got this twice. I did not see it show up on the archive so I'm
assuming it didn't
make it to the mailing list
Karen
> Hi,
>
> I have a fairly large xml file that makes use of a schema. I get the
> following stack trace
>
> java.lang.ArrayIndexOutOfBoundsException: 128
>
Let me take a wild guess... You are using Java 1.2.2 with HotSpot.
Am I right? A lot of people are reporting erroneous array index
expections because HotSpot is buggy. If you are using HotSpot,
please turn it off and try again. If your problem persists, we'll
take a look at it.
P.S. Always include
Content-Type: multipart/mixed;
boundary="C5EA6DD914E762D91D7D63F3"
This is a multi-part message in MIME format.
--C5EA6DD914E762D91D7D63F3
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Hi,
I have a fairly large xml file that makes use of a sc
12 matches
Mail list logo
