"Craig R. McClanahan" wrote:
> Therefore, it seems to me that allowing the configuration of an optional
> "do nothing" SQL command that GenericConnectionPool can use to test the
> validity of the connection would be a better approach. Does that make
> sense to folks?
So, we'd add a testConnection property to control this and also provide
a TestCommand property for the command. Then before returning a
connection, the GCP would try the TestCommand first, and if it generates
an exception, we discard the stale connection and get a new one.
Do you think a default TestCommand of ";" work as a NOP ?
Is there a good way to get a connection to go stale, or do you just have
to wait it out?
I've worked on this area of the code before, and could sign-up for this.
-- Ted Husted, Husted dot Com, Fairport NY USA.
-- Custom Software ~ Technical Services.
-- Tel 716 737-3463.
-- http://www.husted.com/about/struts/
