[
https://issues.apache.org/jira/browse/DERBY-2432?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12504903
]
Knut Anders Hatlen commented on DERBY-2432:
-------------------------------------------
Thanks for investigating this Julo. It also seems like many of the same
questions were asked and answered under DERBY-2508 as well. There weren't any
objections to the approach as far as I could see, so I guess it is
uncontroversial to go for that solution. If there are no objections, I will
commit the patch tomorrow.
Just one final question about the changes in the v4 patch:
> changes:
> XATransactionState:
> - Added a timeout task cancellation to xa_prepare() method.
Will the locks mentioned in the description be released after xa_prepare()? If
they are, this sounds fine.
> 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, d2432_v4.diff, d2432_v4.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.
