db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Daniel John Debrunner (JIRA)" <derby-...@db.apache.org>
Subject [jira] Closed: (DERBY-130) IDENTITY_VAL_LOCAL not reset when new Connection returned from PooledConnection
Date Tue, 11 Jul 2006 23:45:31 GMT
     [ http://issues.apache.org/jira/browse/DERBY-130?page=all ]
     
Daniel John Debrunner closed DERBY-130:
---------------------------------------


> 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.1.1.0, 10.0.2.1
>     Reporter: Daniel John Debrunner
>     Assignee: Daniel John Debrunner
>     Priority: Minor
>      Fix For: 10.1.1.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
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


Mime
View raw message