Return-Path: Delivered-To: apmail-db-derby-dev-archive@www.apache.org Received: (qmail 64819 invoked from network); 25 May 2005 12:29:36 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 25 May 2005 12:29:36 -0000 Received: (qmail 83827 invoked by uid 500); 25 May 2005 12:29:35 -0000 Delivered-To: apmail-db-derby-dev-archive@db.apache.org Received: (qmail 83618 invoked by uid 500); 25 May 2005 12:29:34 -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: "Derby Development" Delivered-To: mailing list derby-dev@db.apache.org Received: (qmail 83601 invoked by uid 99); 25 May 2005 12:29:34 -0000 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests= X-Spam-Check-By: apache.org Received-SPF: pass (hermes.apache.org: local policy) Received: from anchor-post-36.mail.demon.net (HELO anchor-post-36.mail.demon.net) (194.217.242.86) by apache.org (qpsmtpd/0.28) with ESMTP; Wed, 25 May 2005 05:29:32 -0700 Received: from mazumdar.demon.co.uk ([80.177.27.104] helo=pavilion) by anchor-post-36.mail.demon.net with smtp (Exim 4.42) id 1Dav0i-0005PO-MY for derby-dev@db.apache.org; Wed, 25 May 2005 12:29:21 +0000 Message-ID: <000a01c56125$bc8d7ac0$0200000a@lan> From: "Dibyendu Majumdar" To: "Derby Development" References: <54ac72d705051719171a779686@mail.gmail.com> <42935A7F.400@sun.com> <54ac72d705052415473ee5eb7f@mail.gmail.com> <4293E05B.2000108@apache.org> <4293F911.2000106@debrunners.com> <001601c56108$c83e83e0$0200000a@lan> <42946CF4.6020003@sbcglobal.net> Subject: Re: Planning for a 10.1 release Date: Wed, 25 May 2005 13:31:55 +0100 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2800.1409 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1409 X-Virus-Checked: Checked X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N From: "Kathey Marsden" > I think the workaround for DERBY-246, to leave the logical connection > open until the end of the global transaction, should be documented in > the release notes. Hi Kathey, Unfortunately, this is not a workaround. For example, see section 4.2 of JTA spec which describes how an application server would use logical connections. Also, do we know if this is the only problem? I am worried that the DB2 type 4 drivers do not support XA, and if you have ported the DB2 driver, then very likely this won't support XA either. Regards