Return-Path: Delivered-To: apmail-db-derby-dev-archive@www.apache.org Received: (qmail 32410 invoked from network); 26 Nov 2008 10:33:47 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 26 Nov 2008 10:33:47 -0000 Received: (qmail 24609 invoked by uid 500); 26 Nov 2008 10:33:49 -0000 Delivered-To: apmail-db-derby-dev-archive@db.apache.org Received: (qmail 24585 invoked by uid 500); 26 Nov 2008 10:33:49 -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 24550 invoked by uid 99); 26 Nov 2008 10:33:48 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 26 Nov 2008 02:33:48 -0800 X-ASF-Spam-Status: No, hits=-2000.0 required=10.0 tests=ALL_TRUSTED X-Spam-Check-By: apache.org Received: from [140.211.11.140] (HELO brutus.apache.org) (140.211.11.140) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 26 Nov 2008 10:32:28 +0000 Received: from brutus (localhost [127.0.0.1]) by brutus.apache.org (Postfix) with ESMTP id 331B8234C29C for ; Wed, 26 Nov 2008 02:32:45 -0800 (PST) Message-ID: <1935763178.1227695565208.JavaMail.jira@brutus> Date: Wed, 26 Nov 2008 02:32:45 -0800 (PST) From: "Kristian Waagan (JIRA)" To: derby-dev@db.apache.org Subject: [jira] Commented: (DERBY-2532) Client does not return SQLException on XAConnection.getXAResource() on a closed connection, Embedded does In-Reply-To: <6027124.1176098072227.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-2532?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12650932#action_12650932 ] Kristian Waagan commented on DERBY-2532: ---------------------------------------- I'm confused. I thought the problem is that XAConnection.getXAResource() doesn't thrown an exception if the XAConnection is closed? As far as I understand, it should be allowed to call XAConnection.close() several times, and doing this should not result in an exception. So maybe adding a check to see if the connection has been closed in getXAResource would be a fix? This would match the behavior of the embedded driver. > Client does not return SQLException on XAConnection.getXAResource() on a closed connection, Embedded does > --------------------------------------------------------------------------------------------------------- > > Key: DERBY-2532 > URL: https://issues.apache.org/jira/browse/DERBY-2532 > Project: Derby > Issue Type: Bug > Components: Network Client > Affects Versions: 10.3.1.4 > Reporter: Myrna van Lunteren > Assignee: Sabari S Kumar > > In the following scenario from converted test DataSourceTest: > (non-tested code based on the test code) > ---------------- > ClientXADataSource dsx = new ClientXADataSource(); > dsx.setDatabaseName("tstdb"); > XAConnection xac = dsx.getXAConnection(); > XAConnection xac2 = dsx.getXAConnection(); > XAResource xar2 = xac2.getXAResource(); > xac2.close(); > // allow close on already closed XAConnection > xac2.close(); > try { > xac2.getXAResource(); > // Network Server does not think this is worth an exception. > } catch (SQLException sqle) { > System.out.println("expect a 08003 as with Embedded"); > } > ------------------ > With DerbyNetClient, the xac2.getXAResource() does not return an SQLException. > This ought to be documented if expected, or fixed. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.