We aren't actually using the connection pool from Geronimo, just the
transaction manager (JTA/JTS implementation).
But, yes, the connection pool really should manage this whenever
there is a problem opening the connection. Off the top of my head I
don't know what the Minerva library that we use does (though of
course we have all of the source and such), but yes that is the part
of things that should handle this, if the JDBC driver can't...
To be honest, based on the explanation from MySQL and their history
with certain things like, it sounds a bit like an excuse... ;)
-David
On Oct 21, 2006, at 11:11 AM, Sami Siren wrote:
Chris Howe wrote:
Also The "8 hour life" must be parameterized
somewhere, so changing that might be a possibility. In addition,
why not just schedule a simple service
that will hit the database every hour or so.
I would also imagine that a connection pool ..inside...
geronimo?? might be of help in such situations
by testing connections before leasing them.
A quick glance at geronimo docs however did not show
such configuration setting.
--
Sami Siren
