db-derby-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Tony Seebregts <to...@cibecs.com>
Subject Re. PooledConnection being closed
Date Mon, 15 Aug 2005 13:59:23 GMT
Ok, thanks Knut - my misunderstanding. 

I understood the ConnectionPoolDataSource as merely facilitating connection pooling. If it
manages the actual pooling though, is there any point in handling the ConnectionEvents ? Other
than for monitoring/interest ...


Tony Seebregts

>-----Original Message-----
>From: Knut Anders Hatlen [mailto:Knut.Hatlen@Sun.COM] 
>Sent: Monday, August 15, 2005 1:41 PM
>To: Derby Discussion
>Subject: Re: PooledConnection being closed
>Well, the point with pooled connections is that you use
>getConnection() and close() as with ordinary connections, but the
>underlying physical connection is kept open. The Connection object
>returned by getConnection() is a logical connection, and you cannot
>use it after it is closed. If you call getConnection() again, you will
>get a new logical connection, and therefore a new Connection
>object. However, the new logical connection might still use the same
>physical connection.
> -- Knut Anders 

View raw message