commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Juozas Baliuka" <bali...@centras.lt>
Subject Re: [dbcp] Deprecating AbandonedObjectPool
Date Tue, 08 Apr 2003 06:07:43 GMT
Agree, It can be used for debugging, but people missusing it and side effect
can be invissible at development time.

----- Original Message -----
From: "David Graham" <dgraham1980@hotmail.com>
To: <commons-dev@jakarta.apache.org>
Sent: Tuesday, April 08, 2003 3:34 AM
Subject: [dbcp] Deprecating AbandonedObjectPool


> In figuring out bug 18483
> http://nagoya.apache.org/bugzilla/show_bug.cgi?id=18483
>
> I found this thread discussing deprecating the whole retrieval of
abandoned
> connections mechanism.
> http://www.mail-archive.com/commons-dev@jakarta.apache.org/msg19239.html
>
> I agree with Craig that DBCP should never try and grab abandoned
connections
> back into the pool; this is the application's responsibility.  So, I
propose
> we deprecate the 3 classes associated with abandoned connections:
> AbandonedObjectPool, AbandonedTrace, and AbandonedConfig.  I think
> AbandonedObjectPool can simply be replaced with a GenericObjectPool.
>
> Comments?
>
> David
>
>
>
>
> _________________________________________________________________
> Add photos to your e-mail with MSN 8. Get 2 months FREE*.
> http://join.msn.com/?page=features/featuredemail
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: commons-dev-help@jakarta.apache.org
>


---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org


Mime
View raw message