Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: <derby-dev@db.apache.org>
Message-ID: <1387031.1173157584363.JavaMail.root@brutus>
Date: Mon, 5 Mar 2007 21:06:24 -0800 (PST)
From: "Mayuresh Nirhali (JIRA)" <jira@apache.org>
To: derby-dev@db.apache.org
Subject: [jira] Commented: (DERBY-2220) Uncommitted transactions executed
 throught XAResource will held locks after the application terminates (or
 crashes during the transaction).
In-Reply-To: <24350220.1168262307723.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-2220?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12478263 ] 

Mayuresh Nirhali commented on DERBY-2220:
-----------------------------------------

Prashant,

The patch has not made to the derby codebase yet. It will be reviewed 
and committed by one of the committers. As for the release, the 
community has not agreed on any release date for 10.3, but we are 
working towards a release sometime this summer. Also, there is no update 
release planned as of now on top of 10.2.2.

As per derby's integration in glassfish is concerned, I believe that is 
completely handled by the glassfish team and driven by next 
major/minor/update release of glassfish.

Although, there has not been a escalation associated with this 
particular issue, this really is a  internal customer escalation. We 
would like to know about any time constraints you may have regarding 
availability of this fix in glassfish ?? We can work towards that!

Thanks
Mayuresh


> Uncommitted transactions executed throught XAResource will held locks after the application terminates (or crashes during the transaction).
> -------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: DERBY-2220
>                 URL: https://issues.apache.org/jira/browse/DERBY-2220
>             Project: Derby
>          Issue Type: Bug
>    Affects Versions: 10.3.0.0
>         Environment: Solaris Nevada build 49, Sun's JDK1.6
>            Reporter: Julius Stroffek
>         Assigned To: Julius Stroffek
>         Attachments: d2220_beta.diff, d2220_beta2.diff, d2220_try1.diff, d2220_try1.stat, d2220_try2.diff, d2220_try2.stat, d2220_try4.diff, d2220_try4.stat, XATranTest.java, xxx.sql
>
>
> Using this piece of code derby will not release a table lock of 'dummy' table.
>             String query = "insert into dummy (field1) values ('" + Integer.toString(value) + "')";
>             XAConnection xaConnection = createXAConnection("jdbc:derby://localhost:1527/TestDB", "", "");
>             XAResource xaResource = xaConnection.getXAResource();
>             conn = xaConnection.getConnection();
>             
>             Xid xid = createXid(value);        
>             xaResource.setTransactionTimeout(10);
>             xaResource.start(xid, XAResource.TMNOFLAGS);
>             
>             Statement statement = conn.createStatement();
>             statement.execute(query);        
>             
>             // terminate the client application
>             // this will not release any locks
>             System.exit(0);

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