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 <[EMAIL PROTECTED]> 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: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > _______________________________ Do you Yahoo!? Express yourself with Y! Messenger! Free. Download now. http://messenger.yahoo.com --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
