Dirk,
I agree that the behavior is useful, but it gets in the way when you are moving a
legacy application from other connection pools to DBCP.
Besides, except for an extra method call, closing a resource twice causes no harm,
right?
So I think that we should stick with the specification and
What does the community think about adding JMX to Pools/DBCP? What would be the
restrictions imposed?
I'm volunteering to implement it, but I would like to first know if the community
would want such a thing and also if there are any restrictions like no new packages
should be required, etc...
I think that the best way to implement this kind of functionality is through JMX.
Expose the statistics that the pool can gather and let users monitor it and take
action on them by creating monitors and listeners.
This would decouple the management of the pool from its implementation. I think
