> > - Better support/debugging for forcing connections closed after being
> > open for "too long"
> This is exactly what got DBCP into trouble in the past. I'm -1 on
> providing any ability in DBCP to close lost connections. DBCP should
> provide the ability to *log* when it detects a resource leak but the
> application is responsible for the health of the pool.
I understand your view, but do you believe that there is no possible
solution? If it is just an implementation concern, I'd just as soon see
what solution someone comes up with. In your opinion, what are/were the
problems in handling "abandoned" connections in DBCP?
--- Noel
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
