Enhydra database connection pool and MySQL problems

[Petr Stehlik <pstehlik@xxxxxxxxxx>]

Hi,

I've been talking to Mark Matthews (the author of Connector/J, the JDBC
driver for MySQL) about the issues I posted also here not so long ago
(java.io.EOFException). He basically said that Enhydra is doing wrong
thing if it expects a JDBC connection to always remain open. Most
databases discard idle connections sooner or later and if Enhydra does
not do the same sooner than the database the problem pops up.

Am I right that there is NO Enhydra parameter for discarding idle
database connections from the database connection pool?

If there is none, I suggest to add one right now. It would be pretty
similar to SessionManager.MaxIdleTime I guess. Is DODS using the
standard Enhydra database connection pool or would DODS have to be
modified as well?

In the meantime, how can one DISABLE the Enhydra database connection
pool completely so that each connection is opened, used and closed
afterwards? Is there such an option? Setting the MaxPoolSize to 0
doesn't seem to be the right thing.

Thanks for any suggestions or help. This is a serious issue since it
basically renders MySQL unusable with Enhydra, IMHO.

Petr