[
https://issues.apache.org/jira/browse/DERBY-2432?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Julius Stroffek updated DERBY-2432:
-----------------------------------
Attachment: d2432_v3.stat
d2432_v3.diff
The tests (sutes.All and derbyall) for v2 patch finished without errors and
failures.
I am attaching a new version of the patch. I am running the tests now.
Changes compared to a v2 patch:
- Added comment to EmbedXAResource.start about the test of transaction timeout
value to Integer.MAX_VALUE
- CancelXATransactionTask - field tranState removed, synchronization in run
method also removed.
- Monitor.logThrowable - changed as suggested (sorry I missed getPrintWriter
method).
- XATransactionTest - much more detailed comment added to
testXATransactionTimeout method.
- XATransactionTest - removed initialization of xaRes, xaConn and conn before
the for loop.
- XATransactionTest - Assert.fail() added to corresponding try-catch blok when
checking the exception thrown.
I can not see any chance that the tests could fail due to the change in a code
compared to the v2 patch (I ran XATransactionTest alone without failures and
changes has no impact on other tests). However, I'll let you know when my test
run will finish.
> Unimplemented transaction time out for XA transactions may cause that locks
> will not be released when client terminates outside a unit of work.
> -----------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: DERBY-2432
> URL: https://issues.apache.org/jira/browse/DERBY-2432
> Project: Derby
> Issue Type: New Feature
> Components: JDBC
> Reporter: Julius Stroffek
> Assignee: Julius Stroffek
> Fix For: 10.3.0.0
>
> Attachments: d2432.diff, d2432.stat, d2432_v2.diff, d2432_v2.stat,
> d2432_v3.diff, d2432_v3.stat, description.txt
>
>
> The XAResource interface provides function setTransactionTimeout which is
> currently not supported in derby.
> When client application uses client driver to connect to derby database and
> the application crashes outside the unit of work of XA transaction and the
> transaction is not committed or rolled back yet the locks held by the
> transaction will not be released.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
