On Thu, 2004-03-18 at 11:34, Ian Bicking wrote:
> That looks like the right thing to use. Doing it in a database-specific
> way is no problem. It just requires an additional method call in
> getConnection (say, pingConnection), which by default is a no-op, and we
> override it for the various databases.
+1 - yes, please. The DBA who keeps bouncing the SQL server without the
app server is my biggest headache, right above the other DBA who keeps
changing data from under SO and not refreshing the app server...
It would be nice if there was a baked-in mechanism to turn the
connection test off if it effects performance during heavy tasks,
though. I've never benchmarked MySQL's ping, so this may be a pointless
Does the java autocommit test affect performance at all?