[
https://issues.apache.org/jira/browse/DERBY-5166?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13913648#comment-13913648
]
Myrna van Lunteren commented on DERBY-5166:
-------------------------------------------
output with trunk:
Wed Feb 26 14:45:12 PST 2014 : Apache Derby Network Server - 10.11.0.0 alpha -
(1571813) started and ready to accept connections on port 1597
creating or connecting to the database
creating tab (i int, j int) and inserting a row (1,0)
1. create two xids (xid1, xid2) with same gtrid and different branchqualifiers.
2. conn1 = get XA connection
3. xaResource1 = conn1.getXAResource()
4. xaResource1.start(xid1,XAResource.TMNOFLAGS)
5. update row X (set j=1 where i=1) via conn1 (using a Statement.executeUpdate
call)
6. xaResource2 = conn2.getXAResource()
7. xaResource2.start(xid2,XAResource.TMNOFLAGS)
8. update row X (set j=2 where i=1) via conn2
Expected Exception 2 java.sql.SQLTransactionRollbackException: A lock could not
be obtained within the time requested
9. check the value of X via conn1
found the row: 1, 1
Connection ok. got right value
Connection ok. got right value
Got expected XAException org.apache.derby.client.am.XaException: XA_RBTIMEOUT :
Error executing a XAResource.end(), server returned XA_RBTIMEOUT.
> Database internal lock timeouts do not return exceptions on the executeUpdate
> of a jdbc Statement object
> --------------------------------------------------------------------------------------------------------
>
> Key: DERBY-5166
> URL: https://issues.apache.org/jira/browse/DERBY-5166
> Project: Derby
> Issue Type: Bug
> Components: Store
> Affects Versions: 10.6.2.1
> Environment: Mac OSX with Java
> Reporter: Guy Pardon
> Labels: derby_triage10_9
> Attachments: XAReproD5166.java
>
>
> Steps to reproduce:
> 1. create two Xids (xid1, xid2) with the _same_ gtrid value and _different_
> branchqualifiers
> 2. conn1 = get XA connection
> 3. xaResource1 = conn1.getXAResource()
> 4. xaResource1.start(xid1,XAResource.TMNOFLAGS)
> 5. update row X via conn1 (using a Statement.executeUpdate call)
> 6. xaResource2 = conn2.getXAResource()
> 7. xaResource2.start(xid2,XAResource.TMNOFLAGS)
> 8. update row X via conn2
> 9. check the value of X via conn1
> Observed behavior: step 8 hangs for a while (I assume it blocks on a lock and
> times out) and step 9 returns the value from _before_ step 5 - i.e., the
> unchanged, original value.
> The only hypothesis I find consistent with this is the following:
> -step 8 blocks and returns after the transactions are rolled back (and the
> locks released)
> -step 9 then returns the value after rollback, i.e. the original value
> If this is the case, then step 8 should not return OK but rather throw an
> SQLException
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
