commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mario Ivankovits" <Mario.Ivankov...@ops.co.at>
Subject Re: [DBCP] Please let us start to improve the connection pool
Date Tue, 25 Mar 2003 18:26:23 GMT
"Abandoned connection"
If a connection is not released from the application within an specific
time, the pool automatically put this connection back to the pool, thus the
connection is available for one of the next request.

The idea behind this, is to avaoid connection leaks, eg. an application
requests under certain situations more connections without passing back.

e.g.
Thread A requests connection #1
Thread A requests connection #2
Thread A pass back connection#1
Thread A ends

now connection#2 is lost, the pool collects this connection after an
idle-time. Say you have a max of 30 connections in your pool, after 30 calls
to this wrongly programmed thread, no more connection is available, and any
further request to the pool will fail.

----- Original Message -----
From: "Juozas Baliuka" <baliuka@centras.lt>
To: "Jakarta Commons Developers List" <commons-dev@jakarta.apache.org>
Sent: Tuesday, March 25, 2003 6:14 PM
Subject: Re: [DBCP] Please let us start to improve the connection pool


> Is it for drivers like postgresql jdbc ? It returns thread safe connection
> (but I do not trust and do use this feature).
>
> ----- Original Message -----
> From: "Juozas Baliuka" <baliuka@centras.lt>
> To: "Jakarta Commons Developers List" <commons-dev@jakarta.apache.org>
> Sent: Tuesday, March 25, 2003 7:07 PM
> Subject: Re: [DBCP] Please let us start to improve the connection pool
>
>
> >
> > I see I do not understand "abandoned connection" feature, it seems more
> like
> > antipattern than feature.


---------------------------------------------------------------------
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