[
https://issues.apache.org/jira/browse/DERBY-3496?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Knut Anders Hatlen updated DERBY-3496:
--------------------------------------
Attachment: junit-repro.diff
The attached patch (junit-repro.diff) adds a test case to jdbcapi/CallableTest
which fails in both embedded and client/server mode.
$ java junit.textui.TestRunner
org.apache.derbyTesting.functionTests.tests.jdbcapi.CallableTest
....E.............E.........
Time: 6.071
There were 2 errors:
1)
testIsolationLevelChangeAfterFunctionCall(org.apache.derbyTesting.functionTests.tests.jdbcapi.CallableTest)java.sql.SQLException:
Invalid transaction state - held cursor requires same isolation level
....
2)
testIsolationLevelChangeAfterFunctionCall(org.apache.derbyTesting.functionTests.tests.jdbcapi.CallableTest)java.sql.SQLException:
Invalid transaction state - held cursor requires same isolation level
....
> CallableStatement with output parameter leaves cursor open after execution
> --------------------------------------------------------------------------
>
> Key: DERBY-3496
> URL: https://issues.apache.org/jira/browse/DERBY-3496
> Project: Derby
> Issue Type: Bug
> Components: JDBC
> Affects Versions: 10.4.0.0
> Reporter: Knut Anders Hatlen
> Priority: Minor
> Attachments: junit-repro.diff
>
>
> When executing a CallableStatement which has an output parameter, the
> language result set is left open and makes subsequent calls to
> Connection.setTransactionIsolation() fail with "ERROR X0X03: Invalid
> transaction state - held cursor requires same isolation level".
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
