db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Knut Anders Hatlen (JIRA)" <j...@apache.org>
Subject [jira] Commented: (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.
Date Thu, 14 Jun 2007 08:01:29 GMT

    [ https://issues.apache.org/jira/browse/DERBY-2432?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12504588
] 

Knut Anders Hatlen commented on DERBY-2432:
-------------------------------------------

>> Is it specified anywhere what the transaction timeout means? I found a
>> description in the javadoc for XAResource.setTransactionTimeout(), but
>> it doesn't say anything about the effect of the timeout.
>
> No, there is no exact specification what timeout means.

Could you explain the rationale for choosing this particular
behaviour? How do other databases use the timeout?

I'm asking because it is not quite clear to me how the timeout is
used, and what users would expect from the timeout. From the
description of this issue, it seems like the purpose of the timeout is
to ensure that resources are freed if no commit or rollback is
issued. Is this the primary use case for the timeout? If so, is the
code that cancels the running statement necessary? (It does seem to me
that cancelling statements is something one rather would do with a
query timeout than with an XA transaction timeout.) And would it make
more sense to restart the timer each time a method is called on
XAResource, so that the timeout became some sort of idle timeout? (To
avoid cases like: transaction manager calls prepare(), the XAResource
votes OK, and half a second later the XAResource aborts because the
transaction took too long.)

> 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.


Mime
View raw message