Return-Path: Delivered-To: apmail-db-derby-dev-archive@www.apache.org Received: (qmail 49481 invoked from network); 18 Feb 2006 00:54:32 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 18 Feb 2006 00:54:32 -0000 Received: (qmail 70213 invoked by uid 500); 18 Feb 2006 00:54:31 -0000 Delivered-To: apmail-db-derby-dev-archive@db.apache.org Received: (qmail 70189 invoked by uid 500); 18 Feb 2006 00:54:31 -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 70180 invoked by uid 99); 18 Feb 2006 00:54:31 -0000 X-ASF-Spam-Status: No, hits=1.3 required=10.0 tests=SPF_FAIL X-Spam-Check-By: apache.org Received: from [192.87.106.226] (HELO ajax.apache.org) (192.87.106.226) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 17 Feb 2006 16:54:29 -0800 Received: from ajax.apache.org (ajax.apache.org [127.0.0.1]) by ajax.apache.org (Postfix) with ESMTP id 86A92DD for ; Sat, 18 Feb 2006 01:54:08 +0100 (CET) Message-ID: <454091243.1140224048549.JavaMail.jira@ajax.apache.org> Date: Sat, 18 Feb 2006 01:54:08 +0100 (CET) From: "Kathey Marsden (JIRA)" To: derby-dev@db.apache.org Subject: [jira] Created: (DERBY-1006) Client allows setHoldability to HOLD_CURSORS_OVER_COMMIT on both connection and statement MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N Client allows setHoldability to HOLD_CURSORS_OVER_COMMIT on both connection and statement ------------------------------------------------------------------------------------------ Key: DERBY-1006 URL: http://issues.apache.org/jira/browse/DERBY-1006 Project: Derby Type: Bug Versions: 10.1.2.2, 10.3.0.0 Reporter: Kathey Marsden Client allows holdability to be set to HOLD_CURSORS_OVER_COMMIT in a global transaction. I am not sure of the impact on the server side. To reproduce look for this code in checkDataSource30 and take out the return for client. if (!TestUtil.isEmbeddedFramework()) { // Don't run the rest of the test for client // Network XA BUG: Client allows set HOLD_CURSORS_OVER_COMMIT // to be set in a a global transaction on the connection and // statements conn.close(); return; } xid = getXid(24, (byte) 21, (byte) 01); xr.start(xid, XAResource.TMNOFLAGS); System.out.println("CONNECTION(xa) HOLDABILITY " + (conn.getHoldability() == ResultSet.HOLD_CURSORS_OVER_COMMIT)); try { conn.setHoldability(ResultSet.HOLD_CURSORS_OVER_COMMIT); System.out.println("FAIL allowed to set hold mode in xa transaction"); } catch (SQLException sqle) { System.out.println("Expected SQLException(setHoldability) " + sqle.getMessage()); } -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira