db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Mike Matrigali <mikem_...@sbcglobal.net>
Subject Re: [jira] Commented: (DERBY-977) jdbcapi/xaSimplePositive.sql fails
Date Fri, 17 Feb 2006 16:33:13 GMT
If the problem is reproducible then that is probably the most
expedient thing to do, it is very likely the result is JVM
specific as the order tends to be tied to hash algorithms in
the jvm.  Note that background activity can change
the actual # of transactions, but for this particular test so
little is going on it has not been a problem in the past, but
there have been a lot of timing related changes recently.

Long term the best solution for the functionality of this test
would be to write it in java, and have the program deal with
the ordering issues.  Anyone interested in a small amount of
jdbc XA programming?

Myrna van Lunteren wrote:
> Mike,
>  
> I read this to mean we can simply update the masters.
> Or is that not what you meant?
>  
> Thx,
> Myrna
> 
>  
> On 2/16/06, *Mike Matrigali (JIRA)* <derby-dev@db.apache.org 
> <mailto:derby-dev@db.apache.org>> wrote:
> 
>        [
>     http://issues.apache.org/jira/browse/DERBY-977?page=comments#action_12366663
>     <http://issues.apache.org/jira/browse/DERBY-977?page=comments#action_12366663>
>     ]
> 
>     Mike Matrigali commented on DERBY-977:
>     --------------------------------------
> 
>     If you look in the actual test you will see the explanation of this
>     diff:
>     ij(XA)> -- NOTE: The following call to "xa_recover xa_startrscan" is
>     apt to
>     -- return the result set rows in reverse order when changes to
>     -- the Derby engine affect the number of transactions that it takes
>     -- to create a database.  The transactions are stored in a hash table
>     -- based on a global and local id, and when the number of transactions
>     -- changes, the (internal) local id can change, which may lead to a
>     -- change in the result set order.  This order is determined by the
>     -- JVM's hashing algorithm. Examples of changes to the engine that
>     -- can affect this include ones that cause more commits or that
>     -- change the amount of data being stored, such as changes to the
>     -- metadata statements (which is what prompted this explanation in
>     -- the first place).  Ultimately, the problem is that there is no
>     -- way to order the return values from "xa_recover" since it is an
>     -- ij internal statement, not SQL...
>     xa_recover xa_startrscan;
>     Recovered 2 in doubt transactions
>     Transaction 1 : (1,FILTERED,FILTERED)
>     Transaction 2 : (2,FILTERED,FILTERED)
> 
>      > jdbcapi/xaSimplePositive.sql fails
>      > ----------------------------------
>      >
>      >          Key: DERBY-977
>      >          URL: http://issues.apache.org/jira/browse/DERBY-977
>      >      Project: Derby
>      >         Type: Test
>      >   Components: Regression Test Failure
>      >     Versions: 10.2.0.0 <http://10.2.0.0>
>      >  Environment: Solaris 10 3/05 s10_74L2a X86 - SunOS 5.10 Generic,
>     JVM: Sun Microsystems Inc. 1.5.0_04
>      >     Reporter: Ole Solberg
> 
>      >
>      > "Signature":
>      > ********* Diff file xa/xa/xaSimplePositive.diff
>      > *** Start: xaSimplePositive jdk1.5.0_04 xa:xa 2006-02-14 03:03:46 ***
>      > 97 del
>      > < Transaction 1 : (1,FILTERED,FILTERED)
>      > 98 del
>      > < Transaction 2 : (2,FILTERED,FILTERED)
>      > 98a97,98
>      > > Transaction 1 : (2,FILTERED,FILTERED)
>      > > Transaction 2 : (1,FILTERED,FILTERED)
>      > Test Failed.
>      > *** End:   xaSimplePositive jdk1.5.0_04 xa:xa 2006-02-14 03:03:50 ***
>      >
>     http://www.multinet.no/~solberg/public/Apache/TinderBox_Derby/Limited/testSummary-377554.html
>     <http://www.multinet.no/~solberg/public/Apache/TinderBox_Derby/Limited/testSummary-377554.html>
> 
>     --
>     This message is automatically generated by JIRA.
>     -
>     If you think it was sent incorrectly contact one of the administrators:
>       http://issues.apache.org/jira/secure/Administrators.jspa
>     <http://issues.apache.org/jira/secure/Administrators.jspa>
>     -
>     For more information on JIRA, see:
>       http://www.atlassian.com/software/jira
> 
> 


Mime
View raw message