Should connection pools release all resources associated with a Connection when a user calls Connection.close()?
Connection.close() just returns the Connection back to the pool. The
pool that I'm using C3P0 doesn't seem to close any Statement,
PStatement, CStatement, or ResultSets from the Connection.
That doesn't seem right. Are there pools that actually close all
resources but not the Connection itself?
Re: Connection Pooling!! ...Pools are per appdomain, per connection string.... (microsoft.public.dotnet.framework.adonet)
Re: Connection pool count too high? ... just the connection string that determines if a new pool is needed. ... These pools are not destroyed until they are empty for some time ... and the app domain is gone. ... > Our web application is all asp.net, using ADO.NET and SQL Server 2000 STD. ... (microsoft.public.dotnet.framework.adonet)
[ANN] DBPool : JDBC Connection Pooling - v4.7 released ... A new version of DBPool has been released, ... applications that require high performance database access....User-configurable pools to achieve high performance ...User-definable connection validation allows increased reliability ... (comp.lang.java.databases)
[ANN] DBPool : JDBC Connection Pooling - v4.7.2 released ... A new version of DBPool has been released, ... applications that require high performance database access.... * User-configurable pools to achieve high performance ... * User-definable connection validation allows increased reliability ... (comp.lang.java.databases)