2 things can cause this test to fail.
1) a fixed change to the number of transactions in the system at the
point in the test. This is usually a system catalog change somewhere
which results in more or less internal transactions to allocate space on
disk. For this case the test usually breaks, but in exactly the same
way every time on a particular jvm. In that case updating the master
fixes it "this time".
2) Some background timing issue causes the number of transactions to
change. In this case changing the master fixes it sometimes, but
leaves an intermittent diff.
I have not investigated the issue. With test it is usually case 1 and
changing the master for that jvm is the expedient fix. If that is the
case then close it.
Myrna van Lunteren (JIRA) wrote:
[ http://issues.apache.org/jira/browse/DERBY-977?page=comments#action_12368613 ]
Myrna van Lunteren commented on DERBY-977:
------------------------------------------
recouping comments from the list:
" myrna:
I read this to mean we can simply update the masters.
Or is that not what you meant?
mike:
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?
"
I was waiting to see if this would get picked up in line with DERBY-434, but
there it was indicated that the xa*.sql tests would remain in place for jdk13
compatible testing.
However, in the mean time, the test is not failing anymore.
Shall we close this?
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
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
