Hi Thomas and all,
short description about issue:
if Oracle connection closed by some reason (connectivity/firewall/etc), pool continue to keep closed connections and try to use for queries when connectivity restored instead of connection re-new. It's critical for usage of OraclePool.
Issue related only to Oracle (not reproduced in PgPool).
Configuration:
quarkus.version: 2.7.3.Final
vertx-oracle-client: 4.2.5.1
smallrye-mutiny-vertx-oracle-client: 2.18.1
ojdbc11: 21.4.0.0
Full info/logs/steps how to reproduce/logs and comparation with PgPool and Agoral Pool located in github here
All additional info available in README.md
Please ping me if you have some questions or need additional clarifications.