[
https://issues.apache.org/jira/browse/DERBY-3441?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12570799#action_12570799
]
Kristian Waagan commented on DERBY-3441:
----------------------------------------
The ones you mention are not too heavy weight.
What about result sets?
When running some of the tests, I observed lock timeouts. The failing tests
were all SUR tests, and I think the locking behavior might be a bit special
there.
I tried a very experimental patch, where I closed the result sets on logical
statement close and when running suites.All I was down to around 20+
errors/failures (as opposed to around 180).
Most of these I could link to an existing bug.
So even though I can't provide a proper answer now, I do believe there is more
to be handled than what you mentioned above. I'll come back with more info as
soon I as have any.
All of this is a bit in the blue currently, so feedback is very much
appreciated.
I hope to get the basic machinery into place, and then work on issues one by
one from there.
> Determine and implement a proper procedure for resetting a prepared statement
> for reuse in a statement pool
> -----------------------------------------------------------------------------------------------------------
>
> Key: DERBY-3441
> URL: https://issues.apache.org/jira/browse/DERBY-3441
> Project: Derby
> Issue Type: Sub-task
> Components: JDBC, Network Client
> Affects Versions: 10.4.0.0
> Reporter: Kristian Waagan
> Fix For: 10.4.0.0
>
>
> Initial investigations indicate there are no existing suitable methods to
> properly reset a prepared (or callable) statement for reuse with a statement
> pool.
> A full reset is too heavy weight and defeats the purpose of statement
> pooling, but a proper procedure should be achievable by reusing existing
> pieces of code.
> Correctness is of course the most important thing.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
