You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-dev@db.apache.org by "Julius Stroffek (JIRA)" <ji...@apache.org> on 2007/06/07 15:29:26 UTC
[jira] Updated: (DERBY-2432) Unimplemented transaction time out for
XA transactions may cause that locks will not be released when client
terminates outside a unit of work.
[ https://issues.apache.org/jira/browse/DERBY-2432?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Julius Stroffek updated DERBY-2432:
-----------------------------------
Attachment: d2432.stat
d2432.diff
description.txt
I ran derbyall and suites.All without failures.
The description of the patch is in description.txt file. There are some more explanations in DERBY-2508 sub-task.
Please, review the patch and ask questions or post comments.
Thanks.
> 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, 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.