[
https://issues.apache.org/jira/browse/DERBY-2461?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12486075
]
Kathey Marsden commented on DERBY-2461:
---------------------------------------
In converting this test I found what I think may be a bug, but I am not sure.
In testing commit with multiple resultset I see the following lock counts
Embedded
Network Server
autocommit|noautocommit|statement
autocommit|noautocommit|statement
after execution 1 1 1
8 8 8
after next on rs 3 3 3
8 8 8
after values 1 0
8
after getMoreResults 2 2 0
7 7 7
after next on 2nd rs 7 7 0
7 7 7
after getMoreResults 0 7 0
7 7 7
I think the increase in number of locks held after execution and after the
first next is ok because of prefetch, but I think that the locks not being
released after the values 1 statement execution for Network Server and after
the final getMoreResults is a bug. I am not totally sure however and would
appreciate other opinions. The reason that network server holds these locks is
because it retrieves and saves all the resultsets and specifies
getMoreResults(JDBC30Translation.KEEP_CURRENT_RESULT).
> Convert lang/procedure.java to junit
> ------------------------------------
>
> Key: DERBY-2461
> URL: https://issues.apache.org/jira/browse/DERBY-2461
> Project: Derby
> Issue Type: Task
> Components: Test
> Reporter: Jean T. Anderson
> Assigned To: Kathey Marsden
> Priority: Minor
> Attachments: derby-2461-pre.diff
>
>
> Convert the lang/procedure.java test from the old harness to junit.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
