You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-dev@db.apache.org by "Mamta A. Satoor (JIRA)" <ji...@apache.org> on 2008/02/14 07:33:07 UTC

[jira] Commented: (DERBY-3414) In Network server, rollback inside a java procedure does not close the resultsets created before the call to the java procedure.

    [ https://issues.apache.org/jira/browse/DERBY-3414?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12568816#action_12568816 ] 

Mamta A. Satoor commented on DERBY-3414:
----------------------------------------

Added a junit test case for this behavior. The test went into trunk(revision 627673) and 10.3 codeline(revision 627674).

The test case runs in embedded mode to show the correct behavior for rollback inside a java procedure causing all the resultsets to close. The test case for now has been commented out for network server mode and it should be enabled when this jira entry is fixed.

> In Network server, rollback inside a java procedure does not close the resultsets created before the call to the java procedure.
> --------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: DERBY-3414
>                 URL: https://issues.apache.org/jira/browse/DERBY-3414
>             Project: Derby
>          Issue Type: Bug
>          Components: Network Server
>    Affects Versions: 10.2.1.6, 10.2.2.0, 10.3.1.4, 10.3.2.1
>            Reporter: Mamta A. Satoor
>         Attachments: test_rollback_in_procedure.java
>
>
> Inside network server framework, if there is java procedure will rollback inside it, the rollback does not close the resultsets that were created before the call to java procedure was made. This happens in trunk, 10.3 and 10.2 codelines. I haven't tried earlier versions of Derby. In embedded mode, the resultsets (created before the call to java procedure) get closed when the rollback is done inside the java procedure.
> I will soon attach a standalone test case for this behavior.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.