Does this connection provider support aggressive release of JDBC connections and re-acquisition of those connections (if need be) later?
This is used in conjunction with {@link org.hibernate.cfg.Environment#RELEASE_CONNECTIONS}to aggressively release JDBC connections. However, the configured ConnectionProvider must support re-acquisition of the same underlying connection for that semantic to work.
Typically, this is only true in managed environments where a container tracks connections by transaction or thread. Note that JTA semantic depends on the fact that the underlying connection provider does support aggressive release.
@return {@code true} if aggressive releasing is supported; {@code false} otherwise.