Hello
This is my first post to a board here so I hope I am providing enough infromation.

I am running a complex Tomcat Application and in my server XML file I have a resource like this.



My hope was that it would run the validation query when ever I check a connection out of the pool. Instead it runs the query thousands of times. I noticed that even if I put testOnBorrow=false, it still executes the queries. It seems to be doing it once before every SQL call instead of doing it once every 60 seconds per connection. My goal is to automatically get rid of connections that were invalidated by unscheduled database outages. I'm hoping it's jsut something silly I'm doing but can't seem to figure it out.

I played with the min and max active/idle connections thinking the pool was reaching 0 thus treating every connection like a brand new one.

Any thoughts?

Apparently my application is using the default Apache commons dbcp pooling which does not support validation intervals nor does it recognize the testOnBorrow attribute. If a validationQuery exists, it assumes testOnBorrow="true". However without a validationInterval, every borrow of a connection will execute the validation query which is a real problem if your application runs on clusters and runs millions of SQL. I'm going to take a look at the risk vs reward of moving to
org.apache.tomcat.jdbc.pool instead of Apache dbcp. If anyone has any advice, quick setup instructions or thoughts they'd like to share, I'm all ears.