Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: <derby-dev@db.apache.org>
Message-ID: <17133951.1181826388868.JavaMail.jira@brutus>
Date: Thu, 14 Jun 2007 06:06:28 -0700 (PDT)
From: "Julius Stroffek (JIRA)" <jira@apache.org>
To: derby-dev@db.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.
In-Reply-To: <20978358.1173456609289.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

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

    Attachment: d2432_v4.stat
                d2432_v4.diff

I have created an additional patch.

changes:
XATransactionState:
- Added a timeout task cancellation to xa_prepare() method.
- Common code from xa_commit/rollback/prepare moved
  to xa_finalize()
- Some more comments added to cancel()

I am running the tests now. However, the change should not affect the tests. I'll post the results after tests will finish.

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