Hi, Yes, 20% is quite a lot. I see two possibilities for avoiding this: * Don't configure a validation query (explicit configuration of a validation query is not possible for DataSources obtained through JNDI). A major drawback is that broken Connections do not get thrown out of the pool automatically. * We could make it configurable to use the old strategy (i.e., cache Connection and PreparedStatement instances in the ConnectionHelper class and implement connection recovery ourselves) for the cases where performance is a problem.
Best regards, Martijn > -----Original Message----- > From: Thomas Müller [mailto:[email protected]] > Sent: Monday, September 21, 2009 10:41 AM > To: [email protected] > Subject: Re: JCR 1456 Database connection pooling > > Hi, > > > - performance has degraded about 20 percent for mysql and h2 and this > is mostly due to validation queries > > 20% sounds like a lot, I'm wondering how this can be avoided. > > Regards, > Thomas
