db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Tiago R. Espinha (JIRA)" <j...@apache.org>
Subject [jira] Updated: (DERBY-3414) In Network server, rollback inside a java procedure does not close the resultsets created before the call to the java procedure.
Date Mon, 13 Jul 2009 12:05:14 GMT

     [ https://issues.apache.org/jira/browse/DERBY-3414?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Tiago R. Espinha updated DERBY-3414:
------------------------------------

               Urgency: Normal
    Bug behavior facts: [Embedded/Client difference]

Triaged for 10.5.2.

Assigned normal urgency and checked Embedded/Client difference.

> 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.


Mime
View raw message