commons-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Charles Hudak" <>
Subject RE: Connection pooling question
Date Wed, 27 Oct 2004 00:42:44 GMT
This is not really connection pooling. Rather, he has a singleton instance of a connection
that all of the threads of his app share. With so many obvious solutions to pooling out there,
it amazes me that someone would continue to do the wrong thing regarding such a simple premise.
I've been using connection pooling in weblogic and jboss for years and wouldn't even consider
'rolling my own' solution like this.

This WILL NOT SCALE and will be a major contention point between threads in the application.

> -----Original Message-----
> From: Eduardo José Hernández Cisneros 
> [] 
> Sent: Tuesday, October 26, 2004 5:37 PM
> To:
> Subject: Connection pooling question
> 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 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail:
> For additional commands, e-mail:

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message