We are trying to solve problem with DB connection recovery after TCP-IP link dropout.
When the DB connection (connected or connecting) isn’t used in time of network failure, then the AS knows how to remove the ‘old‘ connection a and establish the new one.
But quite different situation is when the DB connection is just executing – info about network failure doesn’t go through JDBC driver to AS and the DB connection remains blocked. This leads to total connection pool blocking with appropriate unpleasant application consequencies. The only solution is AS restart.