Return-Path: Delivered-To: apmail-db-derby-dev-archive@www.apache.org Received: (qmail 90306 invoked from network); 23 May 2006 21:57:11 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 23 May 2006 21:57:11 -0000 Received: (qmail 73081 invoked by uid 500); 23 May 2006 21:57:11 -0000 Delivered-To: apmail-db-derby-dev-archive@db.apache.org Received: (qmail 73041 invoked by uid 500); 23 May 2006 21:57:10 -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 73031 invoked by uid 99); 23 May 2006 21:57:10 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 23 May 2006 14:57:10 -0700 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests= X-Spam-Check-By: apache.org Received: from [209.237.227.198] (HELO brutus.apache.org) (209.237.227.198) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 23 May 2006 14:57:09 -0700 Received: from brutus (localhost [127.0.0.1]) by brutus.apache.org (Postfix) with ESMTP id 9EFA7714283 for ; Tue, 23 May 2006 21:56:30 +0000 (GMT) Message-ID: <15145739.1148421390648.JavaMail.jira@brutus> Date: Tue, 23 May 2006 21:56:30 +0000 (GMT+00:00) From: "Kathey Marsden (JIRA)" To: derby-dev@db.apache.org Subject: [jira] Resolved: (DERBY-1010) setTransactionIsolation can cause ava.sql.SQLException: Invalid operation: statement closed in some contexts with xa In-Reply-To: <1757679367.1140301106573.JavaMail.jira@ajax.apache.org> 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 [ http://issues.apache.org/jira/browse/DERBY-1010?page=all ] Kathey Marsden resolved DERBY-1010: ----------------------------------- Fix Version: 10.1.3.0 10.1.2.4 Resolution: Fixed > setTransactionIsolation can cause ava.sql.SQLException: Invalid operation: statement closed in some contexts with xa > -------------------------------------------------------------------------------------------------------------------- > > Key: DERBY-1010 > URL: http://issues.apache.org/jira/browse/DERBY-1010 > Project: Derby > Type: Bug > Components: Network Client > Versions: 10.2.0.0, 10.1.3.0, 10.1.2.3 > Reporter: Kathey Marsden > Assignee: Kathey Marsden > Fix For: 10.2.0.0, 10.1.3.0, 10.1.2.4 > > With xa setTransactionIsolation can cause a statement closed exception when calling > setTransactionIsolation > Client tries to reuse a statement for sending SET CURRENT ISOLATION statements to the server. There must be some problems with this logic where it is trying to use a closed statement. Perhaps an overall better strategy would be to use an EXCSQLSET to send the set commands to the server and then invoke the embedded JDBC setTransactionIsolation call on the server as Oyvind did for setQueryTimeout. Using the SET ISOLATION statements on the client has caused a variety of problems. > // setTransactionIsolation in some contexts used in this test is > // causing java.sql.SQLException: Invalid operation: statement closed > // error on client. These cases are omitted for now where they cause the > // statement closed error > private static boolean causesStmtClosedOnSetTransactionIsolation = TestUtil.isDerbyNetClientFramework(); > java.sql.SQLException: Invalid operation: statement closed > at org.apache.derby.client.am.SqlException.getSQLException(SqlException.java:280) > at org.apache.derby.client.am.Statement.executeUpdate(Statement.java:437) > at org.apache.derby.client.am.Connection.setTransactionIsolation(Connection.java:911) > at org.apache.derby.client.am.LogicalConnection.setTransactionIsolation(LogicalConnection.java:184) > at org.apache.derbyTesting.functionTests.tests.jdbcapi.checkDataSource.runTest(checkDataSource.java:404) > at org.apache.derbyTesting.functionTests.tests.jdbcapi.checkDataSource.main(checkDataSource.java:119) > Caused by: org.apache.derby.client.am.SqlException: Invalid operation: statement closed > at org.apache.derby.client.am.Statement.checkForClosedStatement(Statement.java:2231) > at org.apache.derby.client.am.Statement.flowExecute(Statement.java:1737) > at org.apache.derby.client.am.Statement.executeUpdateX(Statement.java:442) > at org.apache.derby.client.am.Statement.executeUpdate(Statement.java:428) > ... 4 more > Exception in thread "main" D> -- 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