db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Julius Stroffek (JIRA)" <j...@apache.org>
Subject [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.
Date Wed, 13 Jun 2007 12:24:25 GMT

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

Julius Stroffek updated DERBY-2432:
-----------------------------------

    Attachment: d2432_v2.stat
                d2432_v2.diff

I have created a new patch ran XATransactionTest without any errors or failures. Now I am
running suites.All and derbyall.

I have changed the following:

- Function Monitor.logThrowable created and I am reporting exceptions thrown during a scheduled
rollback using that function.

- A member isFinished created in XATransactionState which indicates that the transaction was
committed or rolled back and this value is checked in 'cancel' method and nothing is done
if the transaction was already committed or rolled back.

- Missing javadoc comments were added.

- The class CancelXATransactionTask changed to be non-static.

- synchronize added to scheduleTimeoutTask method

- call to initCause added in XATransactionState.cancel()

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