The "validationInterval" parameter works prior to other connection validation on Tomcat
Issue
- It takes long time to get healthy connection after DBMS is down and all pooled connection are staled.
- How to keep valid pooled connections in case the connection become invalid due to network/DBMS down?
- I configured Tomcat with both "testOnBorrow" and "testWhileIdle" but it takes more time than I expected.
- Can the connection pool be configured to reload Datasource or JDBC pool connection in case DBMS down?
Environment
- Red Hat JBoss Web Server
- Tomcat 7.x
- Tomcat 8.x
Subscriber exclusive content
A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.