No, there isn't a method doing that. Like you have noticed, the close() method only closes the idle connections in the pool, the active connection will be closed when they are returned to the pool.

If you want to implement this feature, then start with the AbandonedObjectPool.removeAbandoned() method and create a removeAll().

-- Dirk


Meyer, Megan K. wrote:

Hello,

I'm using a BasicDataSource for connection pooling to our database in a
standalone application. The application requires that we have a backup
and restore capability at runtime. We've found that calling close() on
the BasicDataSource doesn't cleanly close all connections to the
database whenever there are active connections that have been borrowed
from the pool.


Is there a way to force all connections in the pool closed, even if
active connections have been lent out?

Thanks in advance,
Megan



--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]



Reply via email to