Return-Path: Delivered-To: apmail-db-derby-dev-archive@www.apache.org Received: (qmail 6786 invoked from network); 3 May 2007 16:47:38 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 3 May 2007 16:47:38 -0000 Received: (qmail 54196 invoked by uid 500); 3 May 2007 16:47:44 -0000 Delivered-To: apmail-db-derby-dev-archive@db.apache.org Received: (qmail 54172 invoked by uid 500); 3 May 2007 16:47:44 -0000 Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: Delivered-To: mailing list derby-dev@db.apache.org Received: (qmail 54162 invoked by uid 99); 3 May 2007 16:47:44 -0000 Received: from herse.apache.org (HELO herse.apache.org) (140.211.11.133) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 03 May 2007 09:47:44 -0700 X-ASF-Spam-Status: No, hits=-100.0 required=10.0 tests=ALL_TRUSTED X-Spam-Check-By: apache.org Received: from [140.211.11.4] (HELO brutus.apache.org) (140.211.11.4) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 03 May 2007 09:47:36 -0700 Received: from brutus (localhost [127.0.0.1]) by brutus.apache.org (Postfix) with ESMTP id A32E6714065 for ; Thu, 3 May 2007 09:47:15 -0700 (PDT) Message-ID: <25631621.1178210835663.JavaMail.jira@brutus> Date: Thu, 3 May 2007 09:47:15 -0700 (PDT) From: "Julius Stroffek (JIRA)" To: derby-dev@db.apache.org Subject: [jira] Commented: (DERBY-2508) Implement the XA transaction timeout support for embedded driver. In-Reply-To: <8306642.1175523512260.JavaMail.jira@brutus> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org [ 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.