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 "Daniel John Debrunner (JIRA)" <de...@db.apache.org> on 2005/01/23 17:43:17 UTC

[jira] Resolved: (DERBY-130) IDENTITY_VAL_LOCAL not reset when new Connection returned from PooledConnection

     [ http://issues.apache.org/jira/browse/DERBY-130?page=history ]
     
Daniel John Debrunner resolved DERBY-130:
-----------------------------------------

     Resolution: Fixed
    Fix Version: 10.1.0.0

> IDENTITY_VAL_LOCAL not reset when new Connection returned from PooledConnection
> -------------------------------------------------------------------------------
>
>          Key: DERBY-130
>          URL: http://issues.apache.org/jira/browse/DERBY-130
>      Project: Derby
>         Type: Bug
>   Components: JDBC
>     Versions: 10.0.2.1, 10.1.0.0
>     Reporter: Daniel John Debrunner
>     Assignee: Daniel John Debrunner
>     Priority: Minor
>      Fix For: 10.1.0.0

>
> With embedded pooled connections identity column values can be leaked from one user's connection to the other. With a PooledConnection the state of IDENTITY_VAL_LOCAL variable is not reset when the underlying EmbeddedConnection is re-used.
> Thus an application can use this function to see a value that was returned to a previous user of the pooled connection.
> A general reset() mechanism is needed on EmbeddedConnection/LanguageConnectionContext, this could replace and encapsulate the current single item that is reset, dropping of session temporary tables.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira