----- Original Message ----- From: "giacomo" <[EMAIL PROTECTED]>
> The HardResourceLimitingPool was choosen because of licensing issues you > might run into when creating more connection than you've licensed. This > way you can be sure you want run into illegality ;) Ok sure, illegality is a bad thing. I guess I have different a expectation of a datasource. I'm used to a temporary unavailability being handled by the connection pooler, not by the application. Are there other connection poolers out there that offer this unreliability? On an unrelated note, I see in Jdbc2Connection (and Jdbc3Connection) there's a m_num_uses which seems to cap the number of times a connection is used to 15. What's the rationale behind this? I'd rather go through hundreds of thousands of statements before it's closed...if my SQL is good, it might take 1ms to run, and some servers take 1000ms to connect. So by capping it to num uses to 15, I've got from 1ms/query to 67ms/query. Just seems like a weird approach. Serge Knystautas Loki Technologies - Unstoppable Websites http://www.lokitech.com/ -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
