Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: <derby-dev@db.apache.org>
Message-ID: <12386170.1181739026137.JavaMail.jira@brutus>
Date: Wed, 13 Jun 2007 05:50:26 -0700 (PDT)
From: "Knut Anders Hatlen (JIRA)" <jira@apache.org>
To: derby-dev@db.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.
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:comment-tabpanel#action_12504218 ] 

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

I looked at the v2 patch. Some additional comments:

I think Monitor.logThrowable() could be simpler:
    t.printStackTrace(getStream().getPrintWriter());

The tranState variable in CancelXATransactionTask is not used.

I believe the synchronization in CancelXATransactionTask.run() is not necessary as this method is the only one that uses that synchronization object, and its only call is to a synchronized method anyway.

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