--- "Laird J. Nelson" <[EMAIL PROTECTED]> wrote:
-----Original Message----- From: John McNally [mailto:[EMAIL PROTECTED] Why is this such a contentious issue?
FWIW, because some users have business experience, and some do not. Those who do recognize that business *runs* on stopgap solutions. The fewer of those stopgap solutions you have to write, the better, IMHO.
[SNIP]
This is absolutely not a DBCP code issue; it is a management issue. Applications that leak resources should have their own separate connection
pool. When they run out of connections, only that app will break and
won't affect any other applications on the server. It will be much easier
to debug the leak in the isolated app because DBCP won't hide it from you
and you won't have to search any other apps.
So, there is no need for this feature in DBCP if the above process is followed. This makes everyone's life simpler :-).
A web application which leaks db connections until it exhausts its pool can impact other applications running on the app server.
What happens is that the broken app ends up sucking up resources for each concurrent request being made to it which is waiting for the db connection timeout. Usually this is set to 5-10 seconds. This can suck up alot of resources. Memory, threads, etc.
Regards,
Glenn
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
