[
https://issues.apache.org/jira/browse/DERBY-3496?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12575323#action_12575323
]
Knut Anders Hatlen commented on DERBY-3496:
-------------------------------------------
If the CallableStatement is closed before the isolation level is changed, it
works in embedded mode, but it still fails the same way in client/server mode.
> 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.
