[snip]
> Sounds ok, but still doesn't entirely solve a problem where a single
> connection might freeze up for a long period of time for some unknown
> reason.
[snip]
Agreed. The connection needn't even freeze; you could have an app that runs
big updates or some really hairy select statements and if too many threads
hit the database at the same time you might hit your cache timeout even with
good code. Very application dependent.
I'll put my thinking cap on.
BTW there's a commented-out wait(1) in getPooledConnection. Anyone know the
history there?
PaulO.
------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Search: <http://www.mail-archive.com/turbine%40list.working-dogs.com/>
Problems?: [EMAIL PROTECTED]
