[
https://issues.apache.org/jira/browse/DERBY-3414?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mamta A. Satoor updated DERBY-3414:
-----------------------------------
Attachment: test_rollback_in_procedure.java
This test program in it's current state is coded to run in Network server mode
and one can see from the output of the test run that resultsets are left open
after the rollback
* Testing with jdbc:derby://localhost:1527/c:/dellater/db;create=true
rs1 still open???????
resultSet still open???????
When the code is changed so it is run in embedded mode, the output is as
follows which shows the expected behavior of resultset closing because of the
rollback inside the java procedure
* Testing with org.apache.derby.jdbc.EmbeddedDriver
closed as expected rs1
closed as expected resultSet
> 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.
