commons-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From David Graham <grahamdavid1...@yahoo.com>
Subject Re: Connection pooling question
Date Wed, 27 Oct 2004 01:44:50 GMT
This "pool" absolutely prevents you from writing any sort of multi step
transaction.  Multiple threads will be corrupting the transaction state by
using the same connection at the same time.  My advice: use a proper
DataSource implementation that actually pools connections.

David

--- Eduardo José Hernández Cisneros <ejhernand3z@hotmail.com> wrote:

> Hi everybody,
> 
>     One friend developed an in-house “connection pooling”, the main idea
> of 
> this component is to open one single database connection. The users
> request 
> for a statements or prepared statements instead of connections. My
> friend 
> calls his component “connection pooling” and probably it is not a
> connection 
> pooling at all. I would like to know the advantages and disadvantages of
> 
> this component in a multithreading application, for example a web 
> application. I am a DBCP and Pool user and to be honest I like them.
> 
> Thanks in advance.
> 
> --Eduardo
> 
> _________________________________________________________________
> Platica con tus amigos en linea con T1msn Messenger 
> http://messenger.t1msn.com.mx/
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: commons-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: commons-user-help@jakarta.apache.org
> 
> 



		
_______________________________
Do you Yahoo!?
Express yourself with Y! Messenger! Free. Download now. 
http://messenger.yahoo.com

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


Mime
View raw message