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

Julius Stroffek commented on DERBY-2508:
----------------------------------------

XAResource.setTransactionTimeout says something about the resource manager's 
default timeout. This should than have some fixed value (or 0 to be disabled).

If derby is used as an embedded database the feature is probably of a limited 
value and using XAResource.setTransactionTimeout might be sufficient. I thought 
that the database administrator might want to change this if derby will run as 
a network server. It might help in case of a network server - the db 
administrator do not have to be able to control the application code and even 
he do not have to know every application connecting to the database.

If the application connecting to derby server will not use 
setTransactionTimeout itself and it will crash when there is some global 
transaction not commited/rolled back which is also not associated to any 
connection, that global transaction will keep holding the locks. DB 
administrator is than able to setup the derby.jdbc.xaTransactionTimeout 
property and the locks would be released after the specified time.

And I thought that it would be a good idea that the behavior of derby network 
client end embedded client would be the same.


> Implement the XA transaction timeout support for embedded driver.
> -----------------------------------------------------------------
>
>                 Key: DERBY-2508
>                 URL: https://issues.apache.org/jira/browse/DERBY-2508
>             Project: Derby
>          Issue Type: Sub-task
>    Affects Versions: 10.2.2.0
>            Reporter: Julius Stroffek
>         Assigned To: Julius Stroffek
>             Fix For: 10.3.0.0
>
>         Attachments: d2432_beta1.diff, d2432_beta1.stat, d2508.diff, 
> d2508.stat
>
>
> Implement the XA transaction support for embedded driver in EmbedXAResource.
> Implement functions XAResource.setTransactionTimeout and 
> XAResource.getTransactionTimeout and add the code to cancel the transaction 
> after the specified period of time.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Reply via email to