What happens with a JDBC connection pool in a MultiPool configuration if a database is shut down?
The MultiPool will detect that a database is down through connection testing while a connection is retrieved from a pool. In other words, the MultiPool does not detect that a database for a JDBC connection pool is down. Instead, it tries to test and if necessary refresh a connection for one certain getConnection() call and, should this fail, will provide a connection from the next pool in the list. For WebLogic Server versions 8.1 SP3 / 7.0 SP5 and upwards, this is changed, i.e., if a connection request to one of the pools in the list fails, the pool is disabled temporarily and checked in regular intervals to see if the database is available again. Please check Enhancements for details.
Related Questions
- How can I disable the first (or any) JDBC connection pool so that the Multipool goes directly to the next pool in the list?
- How do I resume a JDBC connection pool (in a Multipool) after the underlying database is back up again?
- What happens with a JDBC connection pool in a MultiPool configuration if a database is shut down?
