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 "Kristian Waagan (JIRA)" <ji...@apache.org> on 2008/02/23 17:13:19 UTC
[jira] Updated: (DERBY-3457) Closing a logical connection must
close all associated logical statements
[ https://issues.apache.org/jira/browse/DERBY-3457?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kristian Waagan updated DERBY-3457:
-----------------------------------
Summary: Closing a logical connection must close all associated logical statements (was: Closing a logical connection must close all assoicated logical statements)
Fixed typo in summary.
> Closing a logical connection must close all associated logical statements
> -------------------------------------------------------------------------
>
> Key: DERBY-3457
> URL: https://issues.apache.org/jira/browse/DERBY-3457
> Project: Derby
> Issue Type: Task
> Components: JDBC, Network Client
> Affects Versions: 10.4.0.0
> Environment: Client-server with statement pooling enabled in the client driver.
> Reporter: Kristian Waagan
> Assignee: Kristian Waagan
> Fix For: 10.4.0.0
>
>
> When a logical connection is closed, all open logical statements created by this connection must be closed.
> The closing is important per the general principle of cleaning up resources, but especially so in the case of statement pooling, as not closing the logical statement can cause side effects on another logical connection (sharing the same physical connection).
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.