db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Deepa Remesh" <drem...@gmail.com>
Subject Re: [jira] Commented: (DERBY-1533) ArrayIndexOutOfBoundsException in DDMReader, on a specific data size
Date Fri, 04 Aug 2006 14:54:54 GMT
On 8/4/06, Bryan Pendleton (JIRA) <derby-dev@db.apache.org> wrote:
>     [ http://issues.apache.org/jira/browse/DERBY-1533?page=comments#action_12425760 ]
>
> Bryan Pendleton commented on DERBY-1533:
> ----------------------------------------
>
> -Dframework=DerbyNetClient jdbcapi/XATest.java fails even after I reverted my change.
The diff is:
>
> 52a53
> > (1 |PREPARED |false |APP |UserTransaction
> 54d54
> < (1 |PREPARED |false |APP |UserTransaction
> Test Failed.
> *** End:   XATest jdk1.4.2_11 DerbyNetClient 2006-08-04 07:55:58 ***
>
> Looks like the output is in a slightly different order now.
>
> Anybody have an idea why I am seeing this diff in my environment? (Sun 1.4.2, Linux)

DERBY-1640 is open to track this. This looks like an ordering issue. I
had seen it when I had run derbyall with derby-1579 patch though I did
not understand how this patch causes a different order. Maybe we need
to add another order by to the query in the test ?

Thanks,
Deepa

Mime
View raw message