db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Kristian Waagan <Kristian.Waa...@Sun.COM>
Subject Re: ConnectionPoolDataSource properties
Date Thu, 28 Feb 2008 19:20:36 GMT
Daniel John Debrunner wrote:
> Kristian Waagan wrote:
>> Daniel John Debrunner wrote:
> 
>>> A pooling implementation is holding onto PooledConnection objects and 
>>> has some rules for how a logical connection request map to a given 
>>> pool (e.g. database TEST to pool A). If when the PooledConnection was 
>>> created it pointed to database TEST, but now points to database 
>>> PRODUCTION I think that would be a major surprise to a pooling 
>>> implementation.
>>
>> I don't think it's that severe, but my observation does hold for some 
>> properties. As far as I can see, the following data source properties 
>> are definitely updated for a logical connection when 
>> ClientPooledConnection.getConnection() is called:
>>     - user
> 
> User name is severe, I was connecting as DAN but got switched to DBADMIN 
> :-).
> 
> Unlikely to occur in real applications, but the CPDS should not allow this.

Thanks for checking.
I'll log a JIRA issue tomorrow, maybe I gain some more insight until then.


-- 
Kristian

> 
> Dan.


Mime
View raw message