This content has been marked as final. Show 1 reply
If the pool tests a connection and the test fails, that connection will never be re-tested or re-used. It
is closed and discarded immediately and a replacement for it will be made immediately. However, if
the pool experiences two successive occurrences of connections being tested, failing, and for each
of those, the attempt to create a new replacement connection also failed, then WebLogic assumes
the DBMS is down, and disables the pool. Then pool will then try to reconnect every 5 seconds, and
will re-enable the pool at that time. This is not easily changeable in 10.3. How different would it be
if the pool didn't suspend itself, if the DBMS is down?