[
https://issues.apache.org/jira/browse/DERBY-2780?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12503090
]
Knut Anders Hatlen commented on DERBY-2780:
-------------------------------------------
Does the test fail if you rerun it? This test has caused some noise in the past
(even with the same error message as reported here). See DERBY-1320 and
DERBY-1475.
> 10.2 client procedure.java test fails when run against 10.3 server with ERROR
> X0X03: Invalid transaction state - held cursor requires same isolation level
> ----------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: DERBY-2780
> URL: https://issues.apache.org/jira/browse/DERBY-2780
> Project: Derby
> Issue Type: Bug
> Affects Versions: 10.3.0.0
> Reporter: Kathey Marsden
>
> 10.2.1.6 derbyTesting.jar run against 10.3 product jars fails for client for
> lang/procedure.java with:
> It is not clear to me what change caused the difference.
> ERROR X0X03: Invalid transaction state - held cursor requires same isolation
> level
> java.sql.SQLException: Invalid transaction state - held cursor requires same
> isolation level
> at
> org.apache.derby.client.am.SQLExceptionFactory.getSQLException(SQLExceptionFactory.java:46)
> at
> org.apache.derby.client.am.SqlException.getSQLException(SqlException.java:362)
> at
> org.apache.derby.client.am.Statement.executeUpdate(Statement.java:440)
> at
> org.apache.derby.client.am.Connection.setTransactionIsolation(Connection.java:975)
> at
> org.apache.derbyTesting.functionTests.tests.lang.procedure.multipleRSTests(Unknown
> Source)
> at
> org.apache.derbyTesting.functionTests.tests.lang.procedure.runTests(Unknown
> Source)
> at
> org.apache.derbyTesting.functionTests.tests.lang.procedure.main(Unknown
> Source)
> Caused by: org.apache.derby.client.am.SqlException: Invalid transaction state
> - held cursor requires same isolation level
> at
> org.apache.derby.client.am.Statement.completeSqlca(Statement.java:1713)
> at
> org.apache.derby.client.am.Statement.completeExecuteImmediate(Statement.java:1322)
> at
> org.apache.derby.client.net.NetStatementReply.parseEXCSQLIMMreply(NetStatementReply.java:207)
> at
> org.apache.derby.client.net.NetStatementReply.readExecuteImmediate(NetStatementReply.java:58)
> at
> org.apache.derby.client.net.StatementReply.readExecuteImmediate(StatementReply.java:45)
> at
> org.apache.derby.client.net.NetStatement.readExecuteImmediate_(NetStatement.java:125)
> at
> org.apache.derby.client.am.Statement.readExecuteImmediate(Statement.java:1318)
> at org.apache.derby.client.am.Statement.flowExecute(Statement.java:2014)
> at
> org.apache.derby.client.am.Statement.executeUpdateX(Statement.java:445)
> at
> org.apache.derby.client.am.Statement.executeUpdate(Statement.java:431)
> ... 4 more
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
