> But, I've got a feeling that we're talking different languages here! > In fact I was discussing Ken Horn's idea that the pool could > * after a connection has been grabbed but not released, > for say 10 minutes > * forcibly close the underlying real connection > (thus freeing db server's resources) > or forcibly return the real connection to the pool
Sorry, it is a crap and needs no discussions. > * emulate a database server timeout for that connection by > throwing an exception on any further client's call on > the wrapping connection obtained from the pool I understand it and I see meaning in the last option only "throwing an exception", it needs no synchronization. I will be very happy if nobody will add more workarounds to DBCP. > That's what I have been talking about :-) > > -Anton > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
