I don't have one. I'm creating the pool in code. Basically like this:
PoolConfiguration p = new PoolProperties();
p.setUrl(url);
p.setDriverClassName(driverClass);
p.setUsername(username);
p.setPassword(password);
p.setJmxEnabled(true);
p.setTestWhileIdle(true);
p.setTestOnBorrow(true);
p.setTes
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
John,
On 8/11/16 3:33 PM, John Huss wrote:
> I have verified that in version 8.0.36 of tomcat jdbc the
> validation query functionality does not commit the transaction it
> starts in order to run the validation query, which can cause an
> open trans
2016-08-12 13:46 GMT+02:00 John Huss :
> In every database I have used every query requires a transaction. Often
> they will start them automatically if you don't do it explicitly.
Right , but I guess that Tomcat uses JDBC connections and I wonder why
for executing validationQuery sentence, Tomcat
In every database I have used every query requires a transaction. Often
they will start them automatically if you don't do it explicitly.
On Fri, Aug 12, 2016 at 4:13 AM Jose María Zaragoza
wrote:
> 2016-08-11 21:33 GMT+02:00 John Huss :
> > I have verified that in version 8.0.36 of tomcat jdbc t
2016-08-11 21:33 GMT+02:00 John Huss :
> I have verified that in version 8.0.36 of tomcat jdbc the validation query
> functionality does not commit the transaction it starts in order to run the
> validation query, which can cause an open transaction for a very long time
> (possibly until the databa
I have verified that in version 8.0.36 of tomcat jdbc the validation query
functionality does not commit the transaction it starts in order to run the
validation query, which can cause an open transaction for a very long time
(possibly until the database crashes). This seems to be especially
probl
